[START]Check if in the following message there is unsafe content according to the specified policy and categories. Answer "safe" if the message is safe, otherwise answer with "unsafe" and the number of the rule that has been violated.
[BOR]
0: Safe
1: Be civil and nice.
2: Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you *have* to.

[EOR]
[BOC]
One of the scripts I wrote for snazzer [1] provides snapshot measurement [2]. It actually works for any path; it'll generate a report with sha512sum and PGP signature of an entire directory tree, along with shell one-liner to reproduce the measurement again later (or verify signature).

Scroll down a bit from [3] to see an example report, they are designed to be concatenated if you care about accumulating multiple measurement reports.

Edit: here's the sha512sum one-liner (snazzer-receive actually does gpg2 signing and shasumming in parallel to save disk I/O):

    find '../2015-04-16T115421+1000' -xdev -not -path '../2015-04-16T115421+1000'                       \
        -printf '%P\0' | LC_ALL=C sort -z | tar --no-recursion --one-file-system --preserve-permissions \
        --numeric-owner --null --create --to-stdout --directory '../2015-04-16T115421+1000'             \
        --files-from - --exclude-from '../2015-04-16T115421+1000/.snapshot_measurements.exclude' |      \
        sha512sum -b

[1] https://github.com/csirac2/snazzer

[2] https://github.com/csirac2/snazzer/blob/master/doc/snazzer-measure.md

[3] https://github.com/csirac2/snazzer#measuring-snapshots
[EOC]
safe
0
[END]

Safe Be civil and nice. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you *have* to.