P4DTI issue job000252

TitleSupport can't detect tampering with P4DTI source
Assigned userRichard Brooksby
DescriptionPerforce support would like a way to tell whether the person they're talking to has modified the P4DTI code in some way to make it different from the official distribution.
AnalysisProvide a checksum of all the P4DTI files that we don't tell the user to modify. A cryptographically strong checksum (like MD5) would be a nice extra.
How foundcustomer
EvidenceMeeting with Perforce <http://info.ravenbrook.com/mail/2001/02/23/01-10-13/0.txt>.
Observed in1.0.1
Introduced in1.0.0
Created byRichard Brooksby
Created on2001-03-06 15:23:39
Last modified byGareth Rees
Last modified on2001-12-10 19:30:56
History2001-03-06 RB Created.


Change Effect Date User Description
14767 closed 2001-08-07 16:43:39 Gareth Rees Added checksums to the index of releases. Formatted checksum.py as a document. Updated list of files to checksum.
9464 open 2001-03-05 17:05:34 Gareth Rees Added checksum.py, which computes an MD5 hash of the Python source files contributing to the P4DTI and prints it in hexadecimal.