Protecting Zope solution / application -> deploying solutions to customers
Is there a way to protect your intellectual property, if you deliver Zope solutions to customers who have Zope instance running or you will also deploy Zope there. I'm talking about solutions that cosist mostly of some Python based products, Python scripts and page templates -> ie. typical web based site that has some logic, functionality and content, which is accessible through the TTW interface. And even though the client would not have admin account to the Zope instance, they could write a new superuser with zpasswd.py and then get access to everything. My question now is, is there a way to protect your work from being copied, altered or even read in source format? -huima
Hi Heimo, you can make it harder, but you cannot make it impossible. Simply provide very good consistent support and you dont have to fear anybody breaking in the "code". Regards Tino --On Sonntag, 24. November 2002 20:43 +0200 Heimo Laukkanen <huima@fountainpark.org> wrote:
Is there a way to protect your intellectual property, if you deliver Zope solutions to customers who have Zope instance running or you will also deploy Zope there.
I'm talking about solutions that cosist mostly of some Python based products, Python scripts and page templates -> ie. typical web based site that has some logic, functionality and content, which is accessible through the TTW interface. And even though the client would not have admin account to the Zope instance, they could write a new superuser with zpasswd.py and then get access to everything.
My question now is, is there a way to protect your work from being copied, altered or even read in source format?
-huima
_______________________________________________ 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 )
...then how to make it the hardest? :) This is an interesting issue, not only from the intellectual property point of view, but also as a mean to reduce the risks of broken code caused by non-malicious site administrators or authorized users (mainly by lack of knowledge). My reasoning: The hardest is for thirds to perform a change to my released app, the less are the chances that I need to run to fix stuff (thus the greater my time to do new things). Ausum ----- Original Message ----- From: "Tino Wildenhain" <tino@wildenhain.de> To: "Heimo Laukkanen" <huima@fountainpark.org>; <zope@zope.org> Sent: Sunday, November 24, 2002 3:06 PM Subject: Re: [Zope] Protecting Zope solution / application -> deploying solutions to customers
Hi Heimo,
you can make it harder, but you cannot make it impossible. Simply provide very good consistent support and you dont have to fear anybody breaking in the "code".
Regards Tino
--On Sonntag, 24. November 2002 20:43 +0200 Heimo Laukkanen <huima@fountainpark.org> wrote:
Is there a way to protect your intellectual property, if you deliver Zope solutions to customers who have Zope instance running or you will also deploy Zope there.
I'm talking about solutions that cosist mostly of some Python based products, Python scripts and page templates -> ie. typical web based site that has some logic, functionality and content, which is accessible through the TTW interface. And even though the client would not have admin account to the Zope instance, they could write a new superuser with zpasswd.py and then get access to everything.
My question now is, is there a way to protect your work from being copied, altered or even read in source format?
-huima
_______________________________________________ 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 )
_______________________________________________ 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 )
Hi Ausum, the hardest is to host the site yourself. This way nobody can easy break in the code - and if something is not working it is only your fault :-) If there are other people envolved, you might checksum your solutions and if they claim something is broken, just check the sum again. If they have made unauthorized changes - blame them for it. This way software business and not only software busines is made. (Try to change substantial parts of your car and try to blame the manufacturer for it if it is broken)
From the intellectual property point of view I really dont see what might be such a great solution which is so outstanding unique to be worth the challenge to "protect" from other eyes. From my expierience the most protected code is quite sure the ugliest and inefficientest possible. (May be this is often the real reason for protecting it)
Regards Tino --On Sonntag, 24. November 2002 19:52 -0500 Ausum Studio <ausum_studio@hotmail.com> wrote:
...then how to make it the hardest? :)
This is an interesting issue, not only from the intellectual property point of view, but also as a mean to reduce the risks of broken code caused by non-malicious site administrators or authorized users (mainly by lack of knowledge). My reasoning: The hardest is for thirds to perform a change to my released app, the less are the chances that I need to run to fix stuff (thus the greater my time to do new things).
Ausum
----- Original Message ----- From: "Tino Wildenhain" <tino@wildenhain.de> To: "Heimo Laukkanen" <huima@fountainpark.org>; <zope@zope.org> Sent: Sunday, November 24, 2002 3:06 PM Subject: Re: [Zope] Protecting Zope solution / application -> deploying solutions to customers
Hi Heimo,
you can make it harder, but you cannot make it impossible. Simply provide very good consistent support and you dont have to fear anybody breaking in the "code".
Regards Tino
--On Sonntag, 24. November 2002 20:43 +0200 Heimo Laukkanen <huima@fountainpark.org> wrote:
Is there a way to protect your intellectual property, if you deliver Zope solutions to customers who have Zope instance running or you will also deploy Zope there.
I'm talking about solutions that cosist mostly of some Python based products, Python scripts and page templates -> ie. typical web based site that has some logic, functionality and content, which is accessible through the TTW interface. And even though the client would not have admin account to the Zope instance, they could write a new superuser with zpasswd.py and then get access to everything.
My question now is, is there a way to protect your work from being copied, altered or even read in source format?
-huima
_______________________________________________ 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 )
_______________________________________________ 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 )
_______________________________________________ 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 )
From: "Ausum Studio" <ausum_studio@hotmail.com>
This is an interesting issue, not only from the intellectual property point of view, but also as a mean to reduce the risks of broken code caused by non-malicious site administrators or authorized users (mainly by lack of knowledge). My reasoning: The hardest is for thirds to perform a change to my released app, the less are the chances that I need to run to fix stuff (thus the greater my time to do new things).
Do as much as possible as Python products. They'll never find that code, and if they do they won't dare change it. :-)
Pre-compile your python product and external method files and only give them the .pyc files - changing that will cause them some problems. hth Sean Kemplay Lennart Regebro <lennart@regebro.nu> wrote: From: "Ausum Studio"
This is an interesting issue, not only from the intellectual property point of view, but also as a mean to reduce the risks of broken code caused by non-malicious site administrators or authorized users (mainly by lack of knowledge). My reasoning: The hardest is for thirds to perform a change to my released app, the less are the chances that I need to run to fix stuff (thus the greater my time to do new things).
Do as much as possible as Python products. They'll never find that code, and if they do they won't dare change it. :-) _______________________________________________ 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 ) --------------------------------- Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Hi, --On Montag, 25. November 2002 00:59 -0800 Sean K <getmejazzed@yahoo.com> wrote:
Pre-compile your python product and external method files and only give them the .pyc files - changing that will cause them some problems.
Very clever if they choose to run Zope with python -o :/ Regards Tino
hth
Sean Kemplay
Lennart Regebro <lennart@regebro.nu> wrote:
From: "Ausum Studio"
This is an interesting issue, not only from the intellectual property point of view, but also as a mean to reduce the risks of broken code caused by non-malicious site administrators or authorized users (mainly by lack of knowledge). My reasoning: The hardest is for thirds to perform a change to my released app, the less are the chances that I need to run to fix stuff (thus the greater my time to do new things).
Do as much as possible as Python products. They'll never find that code, and if they do they won't dare change it. :-)
_______________________________________________ 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-announcehttp://lists.zope.org /mailman/listinfo/zope-dev )
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
Heimo Laukkanen writes:
Is there a way to protect your intellectual property, if you deliver Zope solutions to customers who have Zope instance running or you will also deploy Zope there.
I'm talking about solutions that cosist mostly of some Python based products Distribute "*.pyc" (and, maybe, "*.pyo" for the (probably) few customers that know about the "-O" option).
, Python scripts and page templates You may consider putting them in a ZODB "product" (e.g. ZClass). A product allows you to control the distribution. You can specify which components are customizable. Only those show source code when they are imported.
It is probably not completely safe... Dieter
Dieter Maurer wrote:
You may consider putting them in a ZODB "product" (e.g. ZClass). A product allows you to control the distribution. You can specify which components are customizable. Only those show source code when they are imported.
I tested this with Zope 2.6.0 on both windows and Linux - and as far as I can tell, even though I selected no distribution and modification only for one object - all the objects were editable. However distributing the product did not work, so atleast something worked as supposed. Can anyone confirm this with their machine - or is there actually more magic to make things not editable, if I make a distribution? Or have I totally misunderstood how the distribution shoud work... -huima
participants (6)
-
Ausum Studio -
Dieter Maurer -
Heimo Laukkanen -
Lennart Regebro -
Sean K -
Tino Wildenhain