>> >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.
I was trying to explain exactly why something like this could be
really useful to the developer community. It's something that Palm really
can't get involved with, but an independant developer could provide a
beneficial resource. Because you're not charging for it, I'm perfectly
happy with waiting awhile. My current protection methods have been
successful so far, but I can foresee a time when someone decides that
they don't like our company's price... =(
I'm not sure if PalmSource 2000 is accepting papers yet, but I'll bet
that 2600 and such would be interested in doing a piece on Palm cracking
(if they haven't already). It would be nicer, though, to be able to
present it to the Palm community, rather than the cracker community... =)
-Rus
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
