> >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....
>
> I wouldn't mind a paper detailing the common methods of hacking Palm
> programs, though...knowledge of this would help to develop methods of
> copy protection that perhaps aren't as orthodox.
>
> Actually, most people use a very heavily published method, namely,
> checking the Hotsync user name. I'd appreciate a paper detailing most
> or all of the common methods of protecting an application, so I can
> have an idea whether or not my particular method is as effective as
> anyone else's or not.
russel, thats exactly what i am going to do, when i get around to it
i know it will be contraversial... but what the hell. i spent 6 months
having fun with crackers and competing with them.. its time i published
it. its the next item on my to-do list..
is PalmSource 2000 accepting papers yet? have they decided on that
issue? i wanted to write this paper especially for PalmSource.
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/
