VC+ built EXE and DLL have inconsistent CRCs

[Guest]

Using Visual Studio we found when you rebuild an EXE file, even if a few minutes later, each time the CRC is different
Same with DLL files

I heard that if you skip a certain number of bytes in the beginning and end of the file, you can get consistent CRC signatures. Anyone knows which bytes to skip

Am open to other suggestions for EXE and DLL authenication

Thanks

 

[Carl Daniel [VC++ MVP]]

Using Visual Studio we found when you rebuild an EXE file, even if a
few minutes later, each time the CRC is different.
Same with DLL files.

I heard that if you skip a certain number of bytes in the beginning
and end of the file, you can get consistent CRC signatures. Anyone
knows which bytes to skip?

Am open to other suggestions for EXE and DLL authenication.

There's a timestamp in the PE header at offste 0xE4 into the file (typical -
you actually need to read the EXE header & skip the stub to find the PE
header in general).

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dndebug/html/msdn_peeringpe.asp
for a discussion of the PE headers & how to interpret them.

-cd