No. I said "if the results of (2) and (4) don't match, you can be sure the file was modified during (3); if they match, that most likely means the file was not modified." and nothing else. There isn't a checksum, hash or anything in the world that will assure this. The larger the checksum range (i.e. the more bits it uses), the lower the probability of a false match. If you need to be absolutely sure, you need a check that has at least the same number of bits as the [ADDED] optimal loss-less compressed version of [/ADDED] the actual file itself. :)
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that.
[The QA section does it automatically now, I hope we soon get it on regular forums as well]
modified on Friday, January 22, 2010 12:56 PM