Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right? Sean -----Original Message----- From: Jerome Alet [mailto:alet@unice.fr] Sent: Tuesday, July 10, 2001 2:55 AM To: J. Cone Cc: zope@zope.org Subject: Re: [Zope] Propietary software with Zope. On Tue, 10 Jul 2001, J. Cone wrote:
The original questioner needed the users of the system to be able to develop their own software, so I think that precludes this security-based model.
I will have the same question eventually, because the server will live in a security domain I don't control. My customer will have root access to the machine, and I may want to discourage them from reading the swearing in the comments in my code :-)
For the filesystem part I suppose that deleting all *.py *.c *.h would do it since Zope should be able to run on *.pyc and *.so alone (I've not tested) For the ZODB I can't see any solution if they have root access. bye, Jerome Alet _______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )
On Tue, 10 Jul 2001 sean.upton@uniontrib.com wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale. Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
On Tue, 10 Jul 2001, Oleg Broytmann wrote:
On Tue, 10 Jul 2001 sean.upton@uniontrib.com wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale.
Into bytecode, which isn't that understandable unless you have a history in languages like FORTH. It's also easily encryptable. Before Zope was open source, all our .pyc modules were encrypted. -Michel
On Tuesday 10 July 2001 13:09, Michel Pelletier wrote:
On Tue, 10 Jul 2001, Oleg Broytmann wrote:
On Tue, 10 Jul 2001 sean.upton@uniontrib.com wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale.
Into bytecode, which isn't that understandable unless you have a history in languages like FORTH.
It's also easily encryptable. Before Zope was open source, all our .pyc modules were encrypted.
this would make a good howto... on a somewhat related note:)... any idea on when the ZPL will be made GPL compatible? ~kapil
On Tuesday 10 July 2001 13:09, Michel Pelletier wrote:
On Tue, 10 Jul 2001, Oleg Broytmann wrote:
On Tue, 10 Jul 2001 sean.upton@uniontrib.com wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale.
Into bytecode, which isn't that understandable unless you have a history in languages like FORTH.
It's also easily encryptable. Before Zope was open source, all our .pyc modules were encrypted.
Just translate your scripts into Perl, it's a pretty good encryption practice.8))
this would make a good howto...
on a somewhat related note:)... any idea on when the ZPL will be made GPL compatible?
~kapil
----- Original Message ----- From: "Gilles Lenfant" <glenfant@bigfoot.com>
It's also easily encryptable. Before Zope was open source, all our
.pyc
modules were encrypted.
Just translate your scripts into Perl, it's a pretty good encryption practice.8))
Hey! I resent that. I like Perl! I'll sue for damages!! Oh, wait, can't do that... I don't live in the States... /dario ;-)
On Tue, 10 Jul 2001, Michel Pelletier wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale.
Into bytecode, which isn't that understandable unless you have a history in languages like FORTH.
I only wanted to say that .pyc files is no protection.
It's also easily encryptable. Before Zope was open source, all our .pyc modules were encrypted.
That I do not understand. Sooner or later you need to decrypt the code to run, so you carry decryption key somewhere nere. Then I take the key and decrypt your .pyc's. I am pretty sure that even hardware encryption is of no big help. This is the lesson all of us must take - bits are copiable. If you want to make money from bits - develop a scheme that does not rely on secrecy. Develop good license, update important information frequently (to make it attractive to subscribe to your service instead of waiting for warez sites), etc. If you rely on secrecy and uncopiable bits - sooner or later your secrets will be published on warez sites, and this will ruin your buisiness. Oleg. ---- Oleg Broytmann http://www.zope.org/Members/phd/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
On Tue, 10 Jul 2001 16:09:47 -0400 (EDT), Michel Pelletier <michel@digicool.com> wrote:
On Tue, 10 Jul 2001, Oleg Broytmann wrote:
On Tue, 10 Jul 2001 sean.upton@uniontrib.com wrote:
Does this work? Even if it didn't I bet that you could just use the .pyc files with dummy .py files created using touch and a file date older than the .pyc file. In theory, this would work, right?
.pyc files are easily decompilabale.
Into bytecode, which isn't that understandable unless you have a history in languages like FORTH.
But it only takes one person (presumably he has a history in forth ;-) to write an automatic pyc to py translator... http://goebel-consult.de/decompyle/ Toby Dickenson tdickenson@geminidataloggers.com
participants (7)
-
Dario Lopez-Kästen -
ender -
Gilles Lenfant -
Michel Pelletier -
Oleg Broytmann -
sean.upton＠uniontrib.com -
Toby Dickenson