Even a simple XOR could be made more complex,
for example, you don't have to XOR -every- byte
in the program ... just XOR a few bytes here
and there until about 30% of them have been
altered. That would be much harder to figure
out than a 100% XORing scheme.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi./sec ... not just a good idea, it's the LAW!
> -----Original Message-----
> From: Aaron Ardiri [mailto:[EMAIL PROTECTED]]
>
> On Fri, 23 Jul 1999, Sergio Carvalho wrote:
> >
> > 2) Put our heads together and come up with some fantastic method for
> > copy protection. There, I think the only efficient option
> would be self
> > modifying code, encrypted somehow, and designed to work on
> only one Palm
> > (by serial no., something )
>
> i currently have a scheme like this.. my latest software Octopus,
> is more protected than my previous..
>
> my previous used some self modifying code, but it used a very
> simple XOR algorithm - so the hacker just needed to know the
> XOR value and then manipulate the data back into its original
> state.
>
> Octopus, which uses a more enhanced algorithm (not just a simple
> XOR anymore).. has not been cracked yet! (yippie) :) - i am
> waiting for them to do it (that is, generate the regcode algorithm)
>
> just remember there are two ways to crack.. :) one by patching,
> the other by extracting your regcode algorithm.
>
> Octopus has been cracked using patching..
>
>
