From the Server Install and Configuration Guide:
"• Once the policy is configured for a project,
Integrity calculates checksums for both text
and binary working files in all Sandboxes of
that project created since the policy was set.
If the current working file size is identical to
the baseline, timestamps are compared.
• Integrity calculatesthe current checksum if
the file timestamps are identical. The
checksum information is then used to
calculate the working file deltas.
• As well as displaying the standard icon for a
working file delta, Integrity displays a
detailed message in the Details panel on the
Integrity Client GUI and a detail message in
the command line interface to indicate when
the checksum is different from its base."
From the Client User Guide:
"If configured by your administrator, checksums will be calculated each time a
new member revision is committed to the archive. The checksums are then
verified when a member revision is received by the Integrity Client. This
ensures data integrity between the Integrity Server and the client.
To determine if a member revision has a checksum, you can run the
si revisioninfo command for the revision and look for the value
assigned to Has Checksum (Yes means that there is a checksum stored for
that revision). For more information on the si revisioninfo command,
see the Integrity CLI Reference for Configuration Management."
So the information is there. Using this information as an official filter is being worked on by our development team. If you like, I can add you to this issue so that you can be kept up to date on the progress of this feature.
