----- Original Message ----- From: "David Smith" <[EMAIL PROTECTED]> To: <delphi-en@yahoogroups.com> Sent: Monday, May 30, 2005 8:59 PM Subject: RE: [list] RE: [delphi-en] Re: GUIDs and the registry
> > The problem with your method is that all a cracker > has to do is recompile your app and replace one bit in > your code: the return value to your question: is my > ini file uncompromised? Then when your routine comes > back claiming the file has been comprimised, that is > the right answer and your app loads! This is true - however I think the assumed level of user he was suggesting protection against is the sort that might know about regedit but wouldn't know how to (properly) drive a debugger to find the correct JE or JNE instruction to modify the check condition. :-) If you want to try and deter slightly more knowledgeable useres then there is of course also the possibility for the application to include a checksum for the exe file itself in the encryped ini file - in that case modifying the exe will also cause that check to fail (of course, that check might also be hax0red)... Also you get exe file packers/encrypters that will make the job of finding and modifying the checking code that much more difficult. Regards Walter ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
