Gidday, > Still fun to think about how to make it difficult for them, even if I > never actually implement any of it :>
It's also always important to remember you are dealing with wetware. That is, crackers are not computers, but people. They look for shortcuts, expect and respond to instant victories, and often move on having done their hack. (This particularly applies to those who crack a piece of software and upload the crack to the Web). Thus, it can be handy to code your protection in such a way that the crack *seems* to work. Then, a few days later, it isn't working again. Gosh, wonder how that happened... Bad cracks like that can drive out good ones in the Internet marketplace <g>. Similarly, don't make the timing of the registration checking too obvious. Emphatically NOT at startup or shutdown or regcode entry time, but perhaps during a semi-random event (e.g. opening the main menu), autosave, a status timer etc. cheers, peter =========================================== Peter Hyde, Development Director, SPIS Ltd, Christchurch, New Zealand * TCompress/TCompLHA component sets for Delphi/Kylix/C++ * TurboNote+: http://TurboNote.com -- top-rated onscreen sticky notes Find all the above and MORE at http://spis.co.nz --------------------------------------------------------------------------- New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED] Website: http://www.delphi.org.nz To UnSub, send email to: [EMAIL PROTECTED] with body of "unsubscribe delphi" Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/
