|
-
Jul 2nd, 2009, 01:16 PM
#1
Thread Starter
Hyperactive Member
[RESOLVED] CRC - Self Referencing Routines
Hello All,
While I have some great CRC routines that examine external programs for tampering before they are launched by my main program, I would also like my main program to look itself over to see if it has been tampered with or perhaps infected by a virus.
Because of the self-referencing problems associated with storing a CRC value within an EXE that will be inspecting itself with that value, I would like to know if you can give me ideas of clever ways to store the CRC value externally, that would in itself be tamper resistant. Either that, or other neat tricks that would allow me to pull off an accurate self CRC-check?
I know that anti-virus programs often check themselves before scanning a system, but what methods are they using that avoids self-referencing problems?
Thanks!
Quiver
P.S. I am aware that people are capable of breaking any security measure when determined, but I still want to try to make my routines tamper resistant.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|