At 09:11 AM 1/21/00 +0000, you wrote:
>It doesn't matter if the comparison is against a fixed day number, a
record limit, though a known
>number makes it easier to search through the assembly code. And it isn't
that difficult,
>although crackers tend to be highly proud of what they do, it's just
child's play and
>requires basic knowledge of assembly and assembly debugging.
>
>I never took the time (never had the need) to invent an elaborate copy
protection scheme.
>As I've suggested in this forum before, when I do write it, I'll probably
base it on
>self-modifying code, with several checksum traps. The best copy protection
scheme will
>probably be based on an encrypting algorithm, and would require
personalized copies.
>
No matter what scheme you use, it's not hard to break it if you have those
basic assembly skills. You can have the most wonderful self-modifying code
in existance, but once it's done modifying itself, it can be pulled out of
memory. The checksum traps (elsewhere in the application I assume) help
somewhat, but hell - all they are is comparisons.
