Frithiof Andreas Jensen
frithiof.jensen at removethis.ted.ericsson.dk
Thu Feb 26 13:03:21 CET 2004
<jbi130 at yahoo.com> wrote in message
news:871xojuckf.fsf at syn.codemonkey.net...
> If this is the case, is the only alternative to hack up the
> interpreter and the bytecode in generates/reads?
.. Which will not stop any dedicated reverse engineering for very long and
probably trigger subtle bugs in extention modules because people will have
made assumptions about how the interpreter works. In any case, it blows up
when the user upgrades Python which will piss the users off (or maybe not:
Java is still around ;)
It would be easiest to stick "the secret bit" on a secure server and access
it via Pyro;
A little harder to stick "the secret bit" in an C/C++ extension module.
In both cases, of course, one can see the interface and the protocol it uses
and "route around the damage" i.e. provide a module that does the same but
is unemcumbered by IPR.
More information about the Python-list