On 30/03/2010 22:34, J. Landman Gay wrote:
Björnke von Gierke wrote:
Be aware that changing a single occuring string in your app to
"hacked by l33t dude" is actually simpler then reverse engineering
the registration code.
Will that work with Rev apps? In my experience, changing almost
anyth
Björnke von Gierke wrote:
Be aware that changing a single occuring string in your app to
"hacked by l33t dude" is actually simpler then reverse engineering
the registration code.
Will that work with Rev apps? In my experience, changing almost anything
in the compiled app causes it to fail to
While I adhere to the private key generated from Customer data model, I have
seen a different paradigm in my market space which is password protecting
the download directory of the fully-enabled version. If the end-user posts
the installer someplace, the software becomes free but oddly enough it
do
Actually most Reg-Key schemes work exactly like that. The Name or email of the
person buying is encoded in some way within the key, or via a reference in a
database. Therefore the ID is tied uniquely to that customer. Of course you
could mail around the program, but that won't help at all agains
I have been thinking about all the cafuffle about registration numbers
and so
forth; and wonder, given the fact that some level of pirating will go on
if a piece
of software is worth anything, if it is really worth all the mucking around.
So:
I should like to float this idea and welcome all r
