> You might get some additional security by compressing the .EXE. We use a
> product called Aspack which compresses the .EXE (code and resources) and
> then decompresses it again as it loads into memory. This would make it
> harder to find the registration code. We use it here mostly because the
> smaller .EXE files load more quickly across a LAN and are easier to
> distribute. Our 3.8MB program turned into a 1.1MB program.
It depends on the level of cracker you aim to protect from. Various means of
creating a different code in memory from that on disk are the stable of anti-cracking
software - and so the debug tools used by the crackers work very much on the
image in memory. If you depend on only one place in the code to protect the code
then life for the cracker is simpler. If are many places with self-modifying code
tied into different features in the program (and provided they dont depend on
one routine for decode and load), then cracker has to hit each one to enable all
features. Hard work though.
Following stuff from http://astalavista.box.sk/ will make your blood run cold. Seems
a lot of people have nothing better to do then help others to steal software.
----------------------------------------------------------
Phil Scadden, Institute of Geological and Nuclear Sciences
PO Box 30368, Lower Hutt, New Zealand
Ph +64 4 5704821, fax +64 4 5704603
---------------------------------------------------------------------------
New Zealand Delphi Users group - Offtopic List - [EMAIL PROTECTED]
Website: http://www.delphi.org.nz
