[Zope] Propietary software with Zope. was: Zope license
zope@zope.org
zope@zope.org
Tue, 10 Jul 2001 15:27:29 GMT
--------------=_4D48009CC0840856B4C0
Content-Description: filename="text1.txt"
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Nobody said it was a licensing issue.=20
Of course it is a security issue (also!). If you develop commercial code=
=20
(Zope, of course), you have no control of the filesystems not the=20
management access of the target system. =20
Get the idea now. ?
>> zpasswd.py -u newuser -p newpasswd" on a fresh zope installation and =
take
>> the "protected" Data.fs to get access into the source code. Or, I am
>> missing something ?
>> How can code be protected in Zope, at least to the same (relative) le=
vel
>> of a compiled object code?
>> This has been a discussion going in our company with some customers a=
s=20
to
>> how to protect developed code...=20
> Just don't give access to the filesystem and the ZODB in management mo=
de,
> to any people you don't want to be able to see the sources. This is a
> security question, not a licensing one. bye, Jerome Alet - alet@u... -=
=20
http://cortex.unice.fr/~jerome
Fac de Medecine de Nice http://wwwmed.unice.fr
Tel: (+33) 4 93 37 76 30 Fax: (+33) 4 93 53 15 15
28 Avenue de Valombrose - 06107 NICE Cedex 2 - FRANCE
--------------=_4D48009CC0840856B4C0
Content-Description: filename="text1.html"
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"CONTENT-TYPE" CONTENT=3D"text/html; charset=3Diso-8=
859-1">
<TITLE>Re: [Zope] Propietary software with Zope. was: Zope license</TIT=
LE>
<META NAME=3D"GENERATOR" CONTENT=3D"StarOffice/5.2 (Linux)">
<META NAME=3D"CREATED" CONTENT=3D"20010710;10234600">
<META NAME=3D"CHANGEDBY" CONTENT=3D"Felipe E. Barousse Boué">
<META NAME=3D"CHANGED" CONTENT=3D"20010710;10272900">
</HEAD>
<BODY>
<P>Nobody said it was a licensing issue.=20
</P>
<P>Of course it is a security issue (also!). If you develop commercial
code (Zope, of course), you have no control of the filesystems not the
management access of the target system. =20
</P>
<P>Get the idea now. ?</P>
<P><BR><BR>
</P>
<P>>> zpasswd.py -u newuser -p newpasswd" on a fresh zope
installation and take</P>
<P>>> the "protected" Data.fs to get access into the
source code. Or, I am</P>
<P>>> missing something ?</P>
<P>>> How can code be protected in Zope, at least to the same
(relative) level</P>
<P>>> of a compiled object code?</P>
<P>>> This has been a discussion going in our company with some
customers as to</P>
<P>>> how to protect developed code...=20
</P>
<P>> Just don't give access to the filesystem and the ZODB in
management mode,</P>
<P>> to any people you don't want to be able to see the sources.
This is a</P>
<P>> security question, not a licensing one. bye, Jerome Alet -
alet@u... - http://cortex.unice.fr/~jerome</P>
<P><BR><BR>
</P>
<P>Fac de Medecine de Nice http://wwwmed.unice.fr</P>
<P>Tel: (+33) 4 93 37 76 30 Fax: (+33) 4 93 53 15 15</P>
<P>28 Avenue de Valombrose - 06107 NICE Cedex 2 - FRANCE</P>
</BODY>
</HTML>
--------------=_4D48009CC0840856B4C0--