At 10:15 AM 6/9/99, you wrote:
>Aaron Ardiri wrote:
> > this means you need to do the following:
> >
> > a) write your algorithm (in C or whatever)
> > b) compile to assembly, get opcodes
> > c) encrypt opcodes, and store in an array,
> > d) when "regcheck" occurs, decrypt, and execute.
>
>I still don't see the point of this. Presumably after you've done all
>this magic, you make some decision: did the regcode check out ok or
>not? A cracker just needs to find this bit of logic and make it look
>like the decision came out "ok". Alternatively, he can find the place
>where you start the regcode process and branch around the whole thing.
>Or am I missing something?
>--Mark
You are absolutely right. Usually a simple NOP will do. We have been fighting
software piracy in the Windows application arena for close to half a decade.
This discussion sounds a lot like those we were having 5 years ago. There are
many techniques that can be used, but one of the first lessons you will learn
is that you do not discuss them in forums such as this one. You can be assured
that these are monitored by those who would attempt to defeat your protection.
