The question remains, do you really want to busy yourself with such extreme
counter measures? I'd rather code and not lose any sleep over those who
spend their time avoiding counter measures.
It's like a cat and mouse game that can't be won. It can be lost though if
you let it get to you.
I'm just doing what I think is 'reasonable deterrant' and don't worry about
the rest. Good for peace of mind. Great for inspiration I'd rather spend on
making my application the very best around. It's also more fun that way.
Ronald Vogelaar
http://www.rovosoft.com
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, September 15, 2006 7:30 PM
Subject: Re: Crackz, what to do ?
So how about a hidden "feature" in the executable code as comments
which isn't really a feature but can be "unlocked" only by tampering
with the code. A statement mentioning that reverse engineering is a
violation of the eula should be included. The true purpose of the
feature would be to email the IP address and any other information that
may identify the cracker. Geolocate can be used on the IP address (it
isn't perfect yet, but it is geting better) so the author can get a
better idea of the location of the cracker.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
