Integrity 10.3: Use Checksums as member filter?

[ssaul]

Hello,

I read the Integrity 10.3 Release Notes and wondered if the new RevisionChecksumsEnabled policy and calulated checksum can be used to filter members.

At the moment, all members with a different timestamp are shown as deltas, with a text like

"Working file newer: 14.02.2013 16:10:55 vs. 08.02.2013 08:24:11"

There is no indication if the file is binary identical, but with different timestamp or if the file size is identical, but some characters changed so the file is not binary identical.

I would like to see only files that are binary different, like "any member deltas", but "any member checksum deltas".

Is this possible or planned?

[jgorsline]

Stephan,

That's a very good question. I am going to forward this question on to the development team and see what they have to say about it. If it's not possible, I will certainly put it in for a future revision!

[ssaul]

Okay, I will patiently wait for an answer of the development team.

[jgorsline · Accepted solution]

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.

[ssaul]

Thanks for showing the right spots in the documentation.

Yes, please add me to this issue so I will be updated on changes.

[jgorsline]

Stephan,

I don't have access to your customer information here in the community. Please give us a quick call or open a case with support so we can add you to this request.

Thanks!