python-ldap-dev — discussion among developers

Re: Very strange problem with module ldapurl

[Jens V. <je...@zo...>]

i was stepping through the creation of l2 in the debugger, and to aid =20=

this i made the following change::

Index: ldapurl.py
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/python-ldap/python-ldap/Lib/ldapurl.py,v
retrieving revision 1.26
diff -r1.26 ldapurl.py
229c229
<     extensions=3DLDAPUrlExtensions({}),
---
 >     extensions=3DNone,
238c238
<     self.extensions=3Dextensions
---
 >     self.extensions=3Dextensions or LDAPUrlExtensions({})

i basically moved the creation of that LDAPUrlExtensions object from =20
the argument list into the function itself. that solved the problem for =20=

me it seems. here is my output now::

l1 before creation of l2:
ldap://host1/????X-=20
BINDPW=3Dpasswd1,dummyext1=3Ddummyvalue1,bindname=3Dcn=3DUser1
l1 after creation of l2:
ldap://host1/????X-=20
BINDPW=3Dpasswd1,dummyext1=3Ddummyvalue1,bindname=3Dcn=3DUser1
l2 itself:
ldap://host2/????X-=20
BINDPW=3Dpasswd2,dummyext2=3Ddummyvalue2,bindname=3Dcn=3DUser2

hmmm.... :)

jens


On Friday, Sep 6, 2002, at 14:27 US/Eastern, Michael Str=F6der wrote:

> HI!
>
> I have a very strange problem with ldapurl (my own source, sigh!) =20
> which can also be a security problem in case of passwords stored in =20=

> LDAPUrlExtension instances. It drives me crazy!
>
> See this simple source:
>
> ------------------------ snip ------------------------
> from ldapurl import LDAPUrl,LDAPUrlExtension
>
> l1=3DLDAPUrl()
> l1.hostport=3D'host1'
> l1.who=3D'cn=3DUser1'
> l1.cred=3D'passwd1'
> l1.extensions['dummyext1']=3DLDAPUrlExtension(
>   extype=3D'dummyext1',exvalue=3D'dummyvalue1'
> )
>
> print 'l1 before creation of l2:\n',str(l1)
>
> l2=3DLDAPUrl()
> l2.hostport=3D'host2'
> l2.who=3D'cn=3DUser2'
> l2.cred=3D'passwd2'
> l2.extensions['dummyext2']=3DLDAPUrlExtension(
>   extype=3D'dummyext2',exvalue=3D'dummyvalue2'
> )
>
> print 'l1 after creation of l2:\n',str(l1)
> print 'l2 itself:\n',str(l2)
> ------------------------ snip ------------------------
>
> In theory l1 and l2 should be completely independent LDAPUrl =20
> instances. But it seems the LDAPUrl.extensions class attributes are =20=

> tied by some means.
>
> The problem is the output (with Python 2.2.1):
>
> $ python Tests/ldapurl_instance_error.py
> ldap://host1/=20
> ????dummyext2=3Ddummyvalue2,dummyext1=3Ddummyvalue1,bindname=3Dcn=3DUser=
2,X-=20
> BINDPW=3Dpasswd2
> ldap://host2/=20
> ????dummyext2=3Ddummyvalue2,dummyext1=3Ddummyvalue1,bindname=3Dcn=3DUser=
2,X-=20
> BINDPW=3Dpasswd2
>
> Anybody here having a clue?
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of that same old
> cell phone?  Get a new here for FREE!
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Very strange problem with module ldapurl

[<mi...@st...>]

HI!

I have a very strange problem with ldapurl (my own source, sigh!) which 
can also be a security problem in case of passwords stored in 
LDAPUrlExtension instances. It drives me crazy!

See this simple source:

------------------------ snip ------------------------
from ldapurl import LDAPUrl,LDAPUrlExtension

l1=LDAPUrl()
l1.hostport='host1'
l1.who='cn=User1'
l1.cred='passwd1'
l1.extensions['dummyext1']=LDAPUrlExtension(
   extype='dummyext1',exvalue='dummyvalue1'
)

print 'l1 before creation of l2:\n',str(l1)

l2=LDAPUrl()
l2.hostport='host2'
l2.who='cn=User2'
l2.cred='passwd2'
l2.extensions['dummyext2']=LDAPUrlExtension(
   extype='dummyext2',exvalue='dummyvalue2'
)

print 'l1 after creation of l2:\n',str(l1)
print 'l2 itself:\n',str(l2)
------------------------ snip ------------------------

In theory l1 and l2 should be completely independent LDAPUrl instances. 
But it seems the LDAPUrl.extensions class attributes are tied by some means.

The problem is the output (with Python 2.2.1):

$ python Tests/ldapurl_instance_error.py
ldap://host1/????dummyext2=dummyvalue2,dummyext1=dummyvalue1,bindname=cn=User2,X-BINDPW=passwd2
ldap://host2/????dummyext2=dummyvalue2,dummyext1=dummyvalue1,bindname=cn=User2,X-BINDPW=passwd2

Anybody here having a clue?

Ciao, Michael.

Re: unable to build ldap.py

[<mi...@st...>]

Ulf von Ceumern wrote:
>     from _ldap import *
> ImportError: ld.so.1: python: fatal: libldap.so.2: open failed: No such file or
> directory

Hmm, on Linux I would start playing with editing /etc/ld.so.conf or 
setting LD_LIBRARY_PATH. No clue about Solaris though.

Ciao, Michael.

Re: unable to build ldap.py

[Ulf v. C. <von...@rz...>]

Ulf von Ceumern wrote:

> Michael Str=F6der wrote:
>
> > > plus: i am installing this under a user dir and need to point pytho=
n to
> > > use this version rather than the old version which is installed und=
er
> > > the python lib dir somewhere. how do i do that?
> >
> > Use the executable of python which is in your user dir when invoking
> > setup.py.
> >
> > Example:
> >
> > $ /home/ulf/bin/python setup.py build
> > $ /home/ulf/bin/python setup.py install
> >
> > instead of
> >
> > $ python setup.py build
> > $ python setup.py install
> >
> > Note that the build also has to be done with your locally installed v=
ersion!
>
> Hi Michael.
>
> Thanks for your help on the warning.
>
> But you got me wrong on the second problem:
>
> I want a python script to use the  python-ldap  version in my home dir =
rather
> than the one installed in the usual dir.  I set
> export
> PYTHONPATH=3D/home/ceumern/ldap/python-ldap-2.0.0pre05/build/lib.solari=
s-2.8-sun4u-2.1/
>
>  and this is what i get:
>
> bash-2.03$ python -d /home/ceumern/ldap/ldap_test.py
> Traceback (most recent call last):
>   File "/home/ceumern/ldap/ldap_test.py", line 6, in ?
>     import ldap
>   File
> "/home/ceumern/ldap/python-ldap-2.0.0pre05/build/lib.solaris-2.8-sun4u-=
2.1/ldap/__init__.py",
> line 11, in ?
>     from _ldap import *
> ImportError: ld.so.1: python: fatal: libldap.so.2: open failed: No such=
 file or
> directory
>
> when i unset the variable the skript uses the version installed under
> python2.1/site-packages/ldap and it works.
> there seems to be something wrong with my built version, but i cannot f=
igure
> out what.
>
> regards, Ulf

I am sorry. I fixed that. i just needed to set the LD_LIBRARY_PATH to whe=
re the libs are..
(newbie :-)

cu, Ulf

Re: unable to build ldap.py

[Ulf v. C. <von...@rz...>]

Michael Str=F6der wrote:

> > plus: i am installing this under a user dir and need to point python =
to
> > use this version rather than the old version which is installed under
> > the python lib dir somewhere. how do i do that?
>
> Use the executable of python which is in your user dir when invoking
> setup.py.
>
> Example:
>
> $ /home/ulf/bin/python setup.py build
> $ /home/ulf/bin/python setup.py install
>
> instead of
>
> $ python setup.py build
> $ python setup.py install
>
> Note that the build also has to be done with your locally installed ver=
sion!

Hi Michael.

Thanks for your help on the warning.

But you got me wrong on the second problem:

I want a python script to use the  python-ldap  version in my home dir ra=
ther
than the one installed in the usual dir.  I set
export
PYTHONPATH=3D/home/ceumern/ldap/python-ldap-2.0.0pre05/build/lib.solaris-=
2.8-sun4u-2.1/

 and this is what i get:

bash-2.03$ python -d /home/ceumern/ldap/ldap_test.py
Traceback (most recent call last):
  File "/home/ceumern/ldap/ldap_test.py", line 6, in ?
    import ldap
  File
"/home/ceumern/ldap/python-ldap-2.0.0pre05/build/lib.solaris-2.8-sun4u-2.=
1/ldap/__init__.py",
line 11, in ?
    from _ldap import *
ImportError: ld.so.1: python: fatal: libldap.so.2: open failed: No such f=
ile or
directory

when i unset the variable the skript uses the version installed under
python2.1/site-packages/ldap and it works.
there seems to be something wrong with my built version, but i cannot fig=
ure
out what.

regards, Ulf

Re: unable to build ldap.py

[<mi...@st...>]

Ulf von Ceumern wrote:
> 
> warning: build_py: file Lib/ldap.py (for module ldap) not found

This is a warning caused by a deficiency of DistUtils. Just ignore it.

> plus: i am installing this under a user dir and need to point python to
> use this version rather than the old version which is installed under
> the python lib dir somewhere. how do i do that?

Use the executable of python which is in your user dir when invoking 
setup.py.

Example:

$ /home/ulf/bin/python setup.py build
$ /home/ulf/bin/python setup.py install

instead of

$ python setup.py build
$ python setup.py install

Note that the build also has to be done with your locally installed version!

Ciao, Michael.

unable to build ldap.py

[Ulf v. C. <von...@rz...>]

Hi.
I have some trouble building and installing  python-ldap-2.0.0pre04 or 5
on my system (dont know sys specs exactly. some sun solaris server).
here is what i get:

bash-2.03$ make
python setup.py build
running build
running build_py
warning: build_py: file Lib/ldap.py (for module ldap) not found
not copying Lib/ldap/__init__.py (output up-to-date)
not copying Lib/ldap/async.py (output up-to-date)
not copying Lib/ldap/functions.py (output up-to-date)
not copying Lib/ldap/sasl.py (output up-to-date)
not copying Lib/ldap/schema.py (output up-to-date)
not copying Lib/ldap/ldapobject.py (output up-to-date)
not copying Lib/ldap/modlist.py (output up-to-date)
not copying Lib/ldapurl.py (output up-to-date)
not copying Lib/ldif.py (output up-to-date)
warning: build_py: file Lib/ldap.py (for module ldap) not found
running build_ext
skipping '_ldap' extension (up-to-date)

plus: i am installing this under a user dir and need to point python to
use this version rather than the old version which is installed under
the python lib dir somewhere. how do i do that?

best regards, ulf v. ceumern

[Fwd: Re: Liberal parsing of schema elements (ITS#1996)]

[<mi...@st...>]

HI!

See final analysis below. Just for the records. Remind when doing error 
handling with wrapped OpenLDAP functions in future.

Ciao, Michael.

-------- Original Message --------
Subject: Re: Liberal parsing of schema elements (ITS#1996)
Date: Thu, 29 Aug 2002 11:00:56 GMT
From: Howard Chu <ope...@Op...>
To: mi...@st...

 > Kurt D. Zeilenga wrote:
 >> I misunderstood the nature of the problem.  The
 >> client library ALLOW flags, if properly enabled,
 >> should be able to parse these non-conformant
 >> values.  If they aren't working, that's a bug.
 >> Patches welcomed.

The code parses the string just fine and returns a valid LDAPObjectClass 
result.
It just happens to leave a non-zero error code set as well, left over 
from its
attempt to find a numeric OID. With the ALLOW flags set, that code is 
ignored
and the parse continues. Since the return value is non-NULL Python 
should not be
treating this as a failure.
 >
 > Any progress on this?
 >
 > Unfortunately I'm not a C programmer. I looked at the OpenLDAP
 > code and AFAICS there is code to allow non-numeric OIDs if the
 > proper ALLOW flag is set.
 >
 > The author of the relevant parts in python-ldap double-checked
 > that the ALLOW flags are properly passed to OpenLDAP's schema
 > parsing functions.
 >
 > But even with LDAP_SCHEMA_ALLOW_ALL the parsing chokes on e.g.
 > this line (Python exception instance displayed here):
 >
 > ldap.schema.SCHERR_NODIGIT: (5, "( pilotOrganization-OID NAME
 > 'pilotOrganization' DESC 'Standard ObjectClass' SUP 'top' MUST (
 > objectclass $ ou $ o )  MAY ( aci $ buildingName $
 > businessCategory $ description $ destinationIndicator $
 > facsimileTelephoneNumber $ internationalIsdnNumber $ l $
 > physicalDeliveryOfficeName $ postOfficeBox $ postalAddress $
 > postalCode $ preferredDeliveryMethod $ registeredAddress $
 > searchGuide $ seeAlso $ st $ street $ telephoneNumber $
 > teletexTerminalIdentifier $ telexNumber $ userPassword $
 > x121Address ) )")

Re: A Query Regarding Python Ldap Form Suman

[<mi...@st...>]

skaich wrote:
>  
> I have recently downloded  python-ldap-2.0.0pre05.tar.gz 
> <http://prdownloads.sourceforge.net/python-ldap/python-ldap-2.0.0pre05.tar.gz?download> from 
> source  forge website. I insalled Python 2.1.2 and Openldap 2.1.4 but 
> when I try to compile the following error message is coming :
 > [..]
> Modules/constants.c: In function `LDAPinit_constants':
> Modules/constants.c:176: `LDAP_FILT_MAXSIZ' undeclared (first use in 
> this function)

This has already been fixed in CVS version.

See comment:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python-ldap/python-ldap/Modules/constants.c 


Or the diff
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/python-ldap/python-ldap/Modules/constants.c.diff?r1=1.13&r2=1.14

Ciao, Michael.

A Query Regarding Python Ldap Form Suman

[skaich <sk...@on...>]

Hello
Sir

I have recently downloded  python-ldap-2.0.0pre05.tar.gz from source  =
forge website. I insalled Python 2.1.2 and Openldap 2.1.4 but when I try =
to compile the following error message is coming :


suse:/usr/local/zope/python-ldap-2.0.0pre05 # /usr/local/bin/python =
setup.py build
running build
running build_py
warning: build_py: file Lib/ldap.py (for module ldap) not found
not copying Lib/ldap/__init__.py (output up-to-date)
not copying Lib/ldap/async.py (output up-to-date)
not copying Lib/ldap/functions.py (output up-to-date)
not copying Lib/ldap/sasl.py (output up-to-date)
not copying Lib/ldap/schema.py (output up-to-date)
not copying Lib/ldap/ldapobject.py (output up-to-date)
not copying Lib/ldap/modlist.py (output up-to-date)
not copying Lib/ldapurl.py (output up-to-date)
not copying Lib/ldif.py (output up-to-date)
warning: build_py: file Lib/ldap.py (for module ldap) not found
running build_ext
building '_ldap' extension
skipping Modules/LDAPObject.c (build/temp.linux-i686-2.1/LDAPObject.o =
up-to-date)
skipping Modules/common.c (build/temp.linux-i686-2.1/common.o =
up-to-date)
gcc -g -O2 -Wall -Wstrict-prototypes -fPIC -DHAVE_LDAP_START_TLS_S =
-DLDAPMODULE_VERSION=3D2.0.0pre05 -IModules =
-I/usr/local/openldap2/include -I/usr/local/include/python2.1 -c =
Modules/constants.c -o build/temp.linux-i686-2.1/constants.o
Modules/constants.c: In function `LDAPinit_constants':
Modules/constants.c:176: `LDAP_FILT_MAXSIZ' undeclared (first use in =
this function)
Modules/constants.c:176: (Each undeclared identifier is reported only =
once
Modules/constants.c:176: for each function it appears in.)
error: command 'gcc' failed with exit status 1

I have installed  openldap in
/usr/local/openldap and I have the following changes the setup.cfg file

[_ldap]

class =3D OpenLDAP2

library_dirs =3D /usr/local/openldap2/lib
include_dirs =3D /usr/local/openldap2/include

Would please help me in this regard.

Waiting for  your feedback

Regards
Suman Aich

A Query Regarding Python Ldap Form Suman

[skaich <sk...@on...>]

Hello
Sir

I have recently downloded  python-ldap-2.0.0pre05.tar.gz from source  =
forge website. I insalled Python 2.1.2 and Openldap 2.1.4 but when I try =
to compile the following error message is coming :


suse:/usr/local/zope/python-ldap-2.0.0pre05 # /usr/local/bin/python =
setup.py build
running build
running build_py
warning: build_py: file Lib/ldap.py (for module ldap) not found
not copying Lib/ldap/__init__.py (output up-to-date)
not copying Lib/ldap/async.py (output up-to-date)
not copying Lib/ldap/functions.py (output up-to-date)
not copying Lib/ldap/sasl.py (output up-to-date)
not copying Lib/ldap/schema.py (output up-to-date)
not copying Lib/ldap/ldapobject.py (output up-to-date)
not copying Lib/ldap/modlist.py (output up-to-date)
not copying Lib/ldapurl.py (output up-to-date)
not copying Lib/ldif.py (output up-to-date)
warning: build_py: file Lib/ldap.py (for module ldap) not found
running build_ext
building '_ldap' extension
skipping Modules/LDAPObject.c (build/temp.linux-i686-2.1/LDAPObject.o =
up-to-date)
skipping Modules/common.c (build/temp.linux-i686-2.1/common.o =
up-to-date)
gcc -g -O2 -Wall -Wstrict-prototypes -fPIC -DHAVE_LDAP_START_TLS_S =
-DLDAPMODULE_VERSION=3D2.0.0pre05 -IModules =
-I/usr/local/openldap2/include -I/usr/local/include/python2.1 -c =
Modules/constants.c -o build/temp.linux-i686-2.1/constants.o
Modules/constants.c: In function `LDAPinit_constants':
Modules/constants.c:176: `LDAP_FILT_MAXSIZ' undeclared (first use in =
this function)
Modules/constants.c:176: (Each undeclared identifier is reported only =
once
Modules/constants.c:176: for each function it appears in.)
error: command 'gcc' failed with exit status 1

I have installed  openldap in
/usr/local/openldap and I have the following changes the setup.cfg file

[_ldap]

class =3D OpenLDAP2

library_dirs =3D /usr/local/openldap2/lib
include_dirs =3D /usr/local/openldap2/include

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[David L. <dav...@it...>]

hmm. for PSF licencing, I think we will have to

=091) check with PSF - they may want us to sign a 'contributor
=09   agreement', a la Zope, to indemnify them against IP/ownership etc
=09   <http://www.python.org/psf/psf-contributor-agreement.html>

=092) assign copyright of all files to the PSF, ie add to each file:
=09  "Copyright (c) 2002 Python Software Foundation; All Rights Reserved"

if you're going to give away ownership like that, then why not just go publ=
ic
domain? its the most 'open' of open source, imho.

I'm happy either way, since I gave up copyright in all of my contributed
files. As, long as you leave the notice/warning message in there somewhere.

note also that previous file versions (extracted from cvs) would remain und=
er
their old licencing/copyright (if any).. which is normal, and desirable.

d

On Fri, 23 Aug 2002, Michael Str=F6der typed thusly:
> Jens Vagelpohl wrote:
> > that looks good.
> >
> > now, all of these licenses mention that they are between the end user
> > and some tangible entity, like the python software foundation in case o=
f
> > the python license. what or who would that entity be for python-ldap? i
> > have a feeling there must be some "licensor" explicitly named to make
> > this beast enforceable at all.
>
> Yes.
>
> How about asking Guido@Zope on how to grant the "licensor" role to
> the PSF? http://www.python.org/psf/mission.html sounds much like
> that. Maybe there's a separate PSF license available we can refer to?
>
> David?
>
> Ciao, Michael.

--=20
David Leonard                           Dav...@it...
School of Inf. Tech. and Elec. Engg _   Ph:+61 404 844 850
The University of Queensland       |+|  http://www.itee.uq.edu.au/~leonard/
QLD 4072  AUSTRALIA               ~` '~

Fwd: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Jens V. <je...@zo...>]

here's guido's answer...

Begin forwarded message:

> From: Guido van Rossum <gu...@py...>
> Date: Fri Aug 23, 2002  11:00:57  US/Eastern
> To: Jens Vagelpohl <je...@zo...>
> Subject: Re: Fwd: License (was: Re: TODO until python-ldap 2.0.0 final=20=

> release)
>
>> guido,
>>
>> here's a non-technical question for you::
>>
>> as part of preparing for the next python-ldap release michael str=88der=
 has
>> started a cleanup of all the various licenses that hang around in the
>> python-ldap repository. his goal is to unify everything under a =
single
>> license and the python/PSF license looks good to all those involved.
>>
>> now here's the hook: there is no entity that we could really name as =
the
>> licensor. michael asked me to ask you if there are any provisions =
under
>> which the python software foundation can assume the position of =
licensor
>> for any non-core python packages?
>>
>> jens
>
> If you transfer the copyright to the PSF, sure!  We haven't quite
> figured out the right way to do that, but draft forms are here:
>
>   http://www.python.org/psf/psf-contributor-agreement.html
>
> There are some alternatives, like joint ownership, too.
>
> --Guido van Rossum (home page: http://www.python.org/~guido/)

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[<mi...@st...>]

Jens Vagelpohl wrote:
 > Michael Str=F6der wrote:
 >
 > >  http://www.python.org/psf/mission.html sounds much like that.
 > > from my read of those pages about the PSF i could not find anything =
that=20
> said the PSF licenses other software packages or offers to somehow be a=
n=20
> umbrella for  python-related software.

My understanding of English is not perfect. That's for sure. Maybe=20
I misunderstood these items on the PSF mission list:

----------------------------- snip -----------------------------
*  Establishes PSF licenses, ensuring the rights of the public to=20
freely obtain, use, redistribute, and modify intellectual property=20
held by the PSF.
[..]
*  Solicits and manages contributions to the Python codebase, and=20
may perform these services on behalf of other open source=20
Python-related codebases.
----------------------------- snip -----------------------------

Let's wait for what Guido and David will answer.

Ciao, Michael.

Fwd: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Jens V. <je...@zo...>]

here's my message to guido...

Begin forwarded message:

> From: Jens Vagelpohl <je...@zo...>
> Date: Fri Aug 23, 2002  09:41:37  US/Eastern
> To: gu...@zo...
> Subject: Fwd: License (was: Re: TODO until python-ldap 2.0.0 final =
release)
>
> guido,
>
> here's a non-technical question for you::
>
> as part of preparing for the next python-ldap release michael str=F6der =
has=20
> started a cleanup of all the various licenses that hang around in the=20=

> python-ldap repository. his goal is to unify everything under a single=20=

> license and the python/PSF license looks good to all those involved.
>
> now here's the hook: there is no entity that we could really name as =
the=20
> licensor. michael asked me to ask you if there are any provisions =
under=20
> which the python software foundation can assume the position of =
licensor=20
> for any non-core python packages?
>
> jens
>
>
> Begin forwarded message:
>
>> From: Jens Vagelpohl <je...@zo...>
>> Date: Fri Aug 23, 2002  09:05:28  US/Eastern
>> To: Michael Str=F6der <mi...@st...>
>> Cc: Python Developer List <pyt...@li...>
>> Subject: Re: License (was: Re: TODO until python-ldap 2.0.0 final =
release)
>>
>> that looks good.
>>
>> now, all of these licenses mention that they are between the end user =
and=20
>> some tangible entity, like the python software foundation in case of =
the=20
>> python license. what or who would that entity be for python-ldap? i =
have=20
>> a feeling there must be some "licensor" explicitly named to make this=20=

>> beast enforceable at all.
>>
>> jens
>>
>>
>> On Friday, August 23, 2002, at 08:54 , Michael Str=F6der wrote:
>>
>>> Jens Vagelpohl wrote:
>>>>> How about using this one: http://www.python.org/2.0.1/license.html
>>>> which one? there's *3* separate licenses in there ;)
>>>
>>> (Sigh!) Well, how about
>>>
>>> PSF LICENSE AGREEMENT FOR PYTHON 2.2.1
>>>
>>> from http://www.python.org/2.2.1/license.html?
>>>
>>> I really wonder what module authors mean by
>>> writing "Python-style license".
>>>
>>> Ciao, Michael.
>>>
>>
>>
>>
>> -------------------------------------------------------
>> This sf.net email is sponsored by: OSDN - Tired of that same old
>> cell phone?  Get a new here for FREE!
>> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
>> _______________________________________________
>> Python-LDAP-dev mailing list
>> Pyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Jens V. <je...@zo...>]

from my read of those pages about the PSF i could not find anything that=20=

said the PSF licenses other software packages or offers to somehow be an=20=

umbrella for  python-related software. i'll send a note to guido and ask=20=

him.

jens


On Friday, August 23, 2002, at 09:16 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>> that looks good.
>> now, all of these licenses mention that they are between the end user =
and=20
>> some tangible entity, like the python software foundation in case of =
the=20
>> python license. what or who would that entity be for python-ldap? i =
have=20
>> a feeling there must be some "licensor" explicitly named to make this=20=

>> beast enforceable at all.
>
> Yes.
>
> How about asking Guido@Zope on how to grant the "licensor" role to the =
PSF?
>  http://www.python.org/psf/mission.html sounds much like that. Maybe =
there'
> s a separate PSF license available we can refer to?
>
> David?
>
> Ciao, Michael.
>

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[<mi...@st...>]

Jens Vagelpohl wrote:
> that looks good.
> 
> now, all of these licenses mention that they are between the end user 
> and some tangible entity, like the python software foundation in case of 
> the python license. what or who would that entity be for python-ldap? i 
> have a feeling there must be some "licensor" explicitly named to make 
> this beast enforceable at all.

Yes.

How about asking Guido@Zope on how to grant the "licensor" role to 
the PSF? http://www.python.org/psf/mission.html sounds much like 
that. Maybe there's a separate PSF license available we can refer to?

David?

Ciao, Michael.

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Jens V. <je...@zo...>]

that looks good.

now, all of these licenses mention that they are between the end user =
and=20
some tangible entity, like the python software foundation in case of the=20=

python license. what or who would that entity be for python-ldap? i have =
a=20
feeling there must be some "licensor" explicitly named to make this =
beast=20
enforceable at all.

jens


On Friday, August 23, 2002, at 08:54 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>>> How about using this one: http://www.python.org/2.0.1/license.html
>> which one? there's *3* separate licenses in there ;)
>
> (Sigh!) Well, how about
>
> PSF LICENSE AGREEMENT FOR PYTHON 2.2.1
>
> from http://www.python.org/2.2.1/license.html?
>
> I really wonder what module authors mean by
> writing "Python-style license".
>
> Ciao, Michael.
>

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[<mi...@st...>]

Jens Vagelpohl wrote:
> 
>> How about using this one: http://www.python.org/2.0.1/license.html
> 
> which one? there's *3* separate licenses in there ;)

(Sigh!) Well, how about

PSF LICENSE AGREEMENT FOR PYTHON 2.2.1

from http://www.python.org/2.2.1/license.html?

I really wonder what module authors mean by
writing "Python-style license".

Ciao, Michael.

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Jens V. <je...@zo...>]

> How about using this one: http://www.python.org/2.0.1/license.html
>

which one? there's *3* separate licenses in there ;)

jens

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[Federico Di G. <fo...@de...>]

Il ven, 2002-08-23 alle 10:39, Michael Str=F6der ha scritto:
> HI!
>=20
> Now that I removed Fog's GPL-ed stuff from the CVS repository I=20
> think it shouldn't be too difficult to choose a common licen(c|s)e=20
> for all files.
>=20
> I have two requirements:
> - be as compatible to Python itself
> - be compatible to GPL
>=20
> http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses=20
> lists the newer Python license as GPL-compatible.
>=20
> How about using this one: http://www.python.org/2.0.1/license.html

good enough for me. maybe my stuff should be kept ouside anyway, i am
spanding almost all my hacking time in other projects nowdays and i
don't know i i'll ever finish the ldap thingies.

ciao,
federico

--=20
Federico Di Gregorio
Debian GNU/Linux Developer & Italian Press Contact        fo...@de...
INIT.D Developer                                           fo...@in...
   God is real. Unless declared integer. -- Anonymous FORTRAN programmer

Re: License (was: Re: TODO until python-ldap 2.0.0 final release)

[<mi...@st...>]

HI!

Now that I removed Fog's GPL-ed stuff from the CVS repository I 
think it shouldn't be too difficult to choose a common licen(c|s)e 
for all files.

I have two requirements:
- be as compatible to Python itself
- be compatible to GPL

http://www.gnu.org/licenses/license-list.html#GPLCompatibleLicenses 
lists the newer Python license as GPL-compatible.

How about using this one: http://www.python.org/2.0.1/license.html

Ciao, Michael.

Re: TLS

[<mi...@st...>]

David Margrave wrote:
> I have finally taken a look atpython-ldap 2.0.  Is there a way to do
> start_tls are are you restricted to ldap.initialize('ldaps://...')?

Use method start_tls_s(). Take a look at Demo/initialize.py.

Ciao, Michael.

TLS

[David M. <da...@es...>]

I have finally taken a look atpython-ldap 2.0.  Is there a way to do
start_tls are are you restricted to ldap.initialize('ldaps://...')?

Dave

Re: TODO until python-ldap 2.0.0 final release

[<mi...@st...>]

Michael Str=F6der wrote:
>=20
> Fog's stuff is not part of the source=20
> distribution package generated with python setup.py sdist anyway.
>=20
> I'd like to also remove it from CVS tree.

/bin/done

Ciao, Michael.