This page was mutated from its original content to reduce and change some links that could confuse integrity.
This was an html rendering of an original raw plaintext email numbered 005530.

best way to check for modification of self

Timothy Newsham newsham at wiliki.eng.hawaii.edu
Fri Jul 30 20:37:33 PDT 1993


> 
> 
> 
> I am looking for C src or algorithms that would be useful for a program
> to check its own integrity and make sure it hasnt been modified.  
> 
> Looking at the filesize of the file would not help, since I want to make
> sure no one has modified just some text, etc.  I would like the algorithm
> or code to be rather quick in doing the check in the initialization of
> the program.  Would finding the src to CRC or sum and adding that into the
> program be the best solution?
> 
> Has anyone else dealt with this?

this is what the tripwire package does. 
I think (perhaps maybe) I heard someone say it uses a hashing
function that is not cryptographically secure (ie. can be forged)
but also that the design is highly modular and the hashing function
can be replaced with something more secure

> Christopher Klaus
> klaus at mail.lds.loral.com cklaus at hotsun.nersc.gov






More information about the cypherpunks-legacy mailing list