Bradley D. Larson
blarson at crary.com
Wed Sep 18 18:59:18 CEST 2002
I might have missed it... (I read most of the posts on this subject).
Why not just use a significant info registration key. The registration
key would be sensative to date, registered name and/or some other
piece of information that would be required to get the software to work.
At least then (if the person buying the pirated software) would have to:
1. Set their computer date BACK to the DATE of the original reg key use.
2. Enter the name of the original owner.
3. Enter the other information (ie. version, address -- if they move they get a
This would do several things.
1. Become pretty obvious to the purchaser that the software is pirated.
2. The pirater and/or purchaser would have to know all items relating to
the reg key.
You could have the reg key checked periodically during the program run time.
Hide the checking routine in some unsuspecting code (create a dummy function
like syncMufflerBelt() in a linked c module that gets called periodically.
If you do come accross an illegal copy you would be able to know the original
owner and possible trace the path to the current user (take 'em all down!).
Terje Johan Abrahamsen wrote:
> If I would like to write some code that would not be possible for others to
> read, after I distribute the program, would Python be suitable? I know that
> there are a few programs like Py2Exe, that creates .exe files. But, I also
> saw this:
> A zip-compatible archive is built, containing all files from this
> directory as well as your script, and appended to a custom python
> interpreter supplied with py2exe.
> Doesn't sound like it is protected very well. Is there some alternative to
> Py2Exe that can do the job, or should I look for a compiled language
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 400 bytes
Desc: Card for Bradley D. Larson
More information about the Python-list