> FINALLY, the last protection scheme that I would use is one where the
> full details of it's operation is published for the world to see....
the PALMOS provides a great mechanism that helps the developer
against cracking :)) most people just overlook it. i figured this
one out when talking to a cracker :))
just a teaser..
if your program uses a pointer to some protected / secret data
(ie: the code generating routine), the hacker can just use debuffer
and dump the memory to a file and then process it as needed.
ask yourself how the PALMOS can help you in regards to memory - and
you can force the hacker to do this memory dump within 8 bytes of
memory - which can in turn be used as a checksum/key for other
fun stuff.. when yuo figure it out, its very nice :)
they need to patch this area to access the data - and patching it
can change a checksum, and affect everything else.. protection is
not a simple do this here type fix. you need to have a sytsem
that uses things sequentially.. if this passes, continue by doing
this.. etc etc..
put some nice dependancies :))
in my paper i will publically explain how my apps are protected.
but let me warn you.. there are dependancies on prc-tools, pilrc
and a few custom utilities i had to write.. thank god for me, all
i need to do now is type:
make
i spent 6 months researching this stuff for fun/challenge.. in
the process i had to learn how to crack (and it is, very easy) :P
this knowledge is taken, and then used to ensure the technique
cannot be used again :)
cheers
az.
--
Aaron Ardiri
Java Certified Programmer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 656 1143 A/H: +46 8 668 78 72
if you enjoy it, then it aint work :) - rule #106 of life
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
