python-ldap-dev — discussion among developers

release versions (was: FYI: ldaptor)

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

Jens Vagelpohl wrote:
> that sounds even worse. however, i was hoping that the "this software is 
> never at any finished state" from the "olden days" would be over soon :)

As long as people are requesting new features appearing in 
OpenLDAP all the time but refuse to test thoroughly CVS versions 
on different platforms with different (build) configuration this 
piece of software won't make any significant progress to a 
non-beta release.

> veryone has a different philosophy about release frequency, i tend to 
> release more often myself.

1. This does not say anything about software quality.

2. If you have full control without many users you can do almost 
everything you want. But people will blame me if their old code 
using python-ldap does not work anymore. Well, you did...

The message is:
python-ldap is community work. Progress is reached by at least 
testing it. And yes, despite the impression some of you might have 
my spare time is tight either.

Ciao, Michael.

Re: FYI: ldaptor

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

that sounds even worse. however, i was hoping that the "this software is=20=

never at any finished state" from the "olden days" would be over soon :)

veryone has a different philosophy about release frequency, i tend to=20
release more often myself.

jens


On Friday, July 19, 2002, at 10:52 , Michael Str=F6der wrote:

> Jens Vagelpohl wrote:
>> i was thinking of dropping support for python-ldap < 2.0 in new =
releases=20
>> of some of my python products. the problem that came to mind was that=20=

>> people might be reluctant to switch to the latest python-ldap version=20=

>> because the current release name, "2.0.0pre4", makes it sound like =
it's=20
>> not a finished release.
>
> BTW: Everybody use 1.10alpha3. How does that sound to you...?
>
> Ciao, Michael.

Re: FYI: ldaptor

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

Jens Vagelpohl wrote:
> 
> i was thinking of dropping support for python-ldap < 2.0 in new releases 
> of some of my python products. the problem that came to mind was that 
> people might be reluctant to switch to the latest python-ldap version 
> because the current release name, "2.0.0pre4", makes it sound like it's 
> not a finished release.

BTW: Everybody use 1.10alpha3. How does that sound to you...?

Ciao, Michael.

Re: FYI: ldaptor

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

Jens Vagelpohl wrote:
> 
> i was thinking of dropping support for python-ldap < 2.0 in new releases 
> of some of my python products. the problem that came to mind was that 
> people might be reluctant to switch to the latest python-ldap version 
> because the current release name, "2.0.0pre4", makes it sound like it's 
> not a finished release.

Indeed it's not finished yet. Hence "pre".

I would be willing to release a "2.0.0pre05" soon.

> here's my question: since we all have been using 2.0.0pre4 very 
> successfully (at least i have), would it be too much work to roll a 
> 2.0.0 release either from 2.0.0pre4 or a later CVS-state?

We did not use 2.0.0pre4 "very successfully". Remember the issues 
with performance fixed in current CVS? Remember open issues with 
libldap_r and thread-locking?

I don't yet have much feedback of tests done with current CVS 
version. I usually don't get much feedback if I ask questions like 
"any objections against removing xyz...".

Ciao, Michael.

Re: FYI: ldaptor

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

hi michael et al,

i was thinking of dropping support for python-ldap < 2.0 in new releases 
of some of my python products. the problem that came to mind was that 
people might be reluctant to switch to the latest python-ldap version 
because the current release name, "2.0.0pre4", makes it sound like it's 
not a finished release. i would be much more comfortable to tell people 
"get python-ldap 2.0.0" instead of "get python-ldap 2.0.0pre4".

here's my question: since we all have been using 2.0.0pre4 very 
successfully (at least i have), would it be too much work to roll a 2.0.0 
release either from 2.0.0pre4 or a later CVS-state?

jens

Re: [Fwd: libldap_r: undefined symbol: ldap_first_reference (ITS#1922)]

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

Joe Little wrote:
> I did note the new 2.1.3 update too, and saw the libldap_r 
> build fix. Did you get a separate email from Kurt saying that it was 
> going to be addressed in a 2.0.x release as well?

The fix appeared in the REL_ENG_2 either.

----------------------------
revision 1.57
date: 2002/07/08 22:34:41;  author: kurt;  state: Exp;  lines: +8 -7
ITS#1922: add references.lo
----------------------------

No release yet.

Ciao, Michael.

Re: python-LDAP on Win32

[Mauro C. <mci...@si...>]

Richard Ferry wrote:

>This is going to be put into a production environment, so I am hesitant to play w/ something experimental. What is your experience with it?
>
Well, the new version appears to work fine on my system; but I have no 
time to thoroughly test every feature.

Mind that it's just a straightforward compilation of the same codebase 
everybody else's using, only done with MSVC++ (Win32, Intel). There are 
some quirks to the build process, but other than that, it compiles quite 
smoothly.

>Re: the  UMich libraries, are there any install instructions for this on a Win32 system?
>  
>
You just have to put the DLLs on your PATH. There's two of them, if I 
remember correctly, and both are needed; they were usually found 
(already compiled) on the UMich website.

I may send you working (albeit old) binaries, if you have problems 
finding them.

BR,
Mauro

Caching-related DEFINE's

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

HI!

Anyone here in favor of caching features in OpenLDAP2 libs? This 
feature is considered to be broken/experimental. Therefore I'd 
like to comment out the cache-related defines in setup.py.

Comments?

Ciao, Michael.

Re: newbie

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

"Learning Python" is a very good book that can help you deal with simple 
python data types... ;)

print x[1]['uid']

jens


On Wednesday, July 17, 2002, at 09:10 , Klaus Boehm wrote:

> can anyone tell me how i can obtain the value from an attributetype(uid)
>
> from a user profile in ldap?
>
> this is my code:
>
> import ldap
> l = ldap.initialize("ldap://ldap.dmg.ewt.de:389")
>
> l.simple_bind_s("cn=admin, o=xxx", "xxxxxx")
> x = l.search_s("ou=People, o=xxx", ldap.SCOPE_ONELEVEL, "gecos=xxxxxx",
> attrlist=['uid'], attrsonly=0)
> print x
> or
> print x[0]
>
> ('cn=klausboehm, ou=People, o=xxx', {'uid': ['value']})
>
> the output is a list with one index.
> how can i extract the value from the attribute uid?
>
>
> thanks for help
>
> klaus
>
> --
>
> ewt gmbh
> data management group
> tel: ++49 821 3106 319
> fax: ++49 821 3106 399
> url: www.ewt.de
>
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

newbie

[Klaus B. <k....@ew...>]

can anyone tell me how i can obtain the value from an attributetype(uid)

from a user profile in ldap?

this is my code:

import ldap
l = ldap.initialize("ldap://ldap.dmg.ewt.de:389")

l.simple_bind_s("cn=admin, o=xxx", "xxxxxx")
x = l.search_s("ou=People, o=xxx", ldap.SCOPE_ONELEVEL, "gecos=xxxxxx",
attrlist=['uid'], attrsonly=0)
print x
or
print x[0]

('cn=klausboehm, ou=People, o=xxx', {'uid': ['value']})

the output is a list with one index.
how can i extract the value from the attribute uid?


thanks for help

klaus

--

ewt gmbh
data management group
tel: ++49 821 3106 319
fax: ++49 821 3106 399
url: www.ewt.de

Re: (no subject)

[Mauro C. <mci...@si...>]

rf...@vo... wrote:

>Hi !
>
>I'm new to python and need a connection to our ldap via python. I have downloaded the win32 version, _ldap.pyd and ldap.py. 
>
>The readme file for win32 says that is "NOT SAFE" for multi-threading, but the file itself has a date mark of 1996.
>
>Is this the version I should use or has it been updated to a version that is safe ?
>
>I don't see any real install instructions (other than the readme) and I don't see any actual examples of how the calls s/b done. Does anyone know of anywhere I can get some real-life examples of binds, searches, modifies ? The included help files don't have install instructions.
>
>Thanks,
>Richard Ferry
>  
>
The multithreading part is not there yet. It's a newish development in 
the main tree; I haven't got the time to do it now for the Win32 part. I 
hope it will get there in the next few weeks.

However, there is indeed a newer version under Win32, linked against 
OpenLDAP 2.0.23 instead of the old UMich libraries. It seems to work, 
but it's still in an experimental phase; if you wish to test it I may 
send the installer to you. Mind though that it's for Python 2.2.

You also need to have the SASL DLL on your path. I may provide that if 
necessary.

Mauro

(no subject)

[<rf...@vo...>]

Hi !

I'm new to python and need a connection to our ldap via python. I 
have downloaded the win32 version, _ldap.pyd and ldap.py. 

The readme file for win32 says that is "NOT SAFE" for multi-threading, 
but the file itself has a date mark of 1996.

Is this the version I should use or has it been updated to a version 
that is safe ?

I don't see any real install instructions (other than the readme) and I 
don't see any actual examples of how the calls s/b done. Does 
anyone know of anywhere I can get some real-life examples of binds, 
searches, modifies ? The included help files don't have install 
instructions.

Thanks,
Richard Ferry

Re: Accessing openLDAP Server from Python Script inside a Zope CMF.

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

this is a Zope question, not a python-ldap question.

the simple solution: put the code into an external method instead of 
a python script.

the hard solution: look into the documentation for the pythonscript 
product itself to find out how to enable access to outside modules.

zope security is doing its job here. you cannot just willy-nilly 
import stuff in a script that can be edited through the web, it's a 
security disaster waiting to happen. that's why zope disallows what 
you are trying to do by default.

jens


On Tuesday, July 16, 2002, at 04:42 , Ashish Gautam wrote:

> Hi all,
> I am trying to access openLDAP server from a python script inside 
> CMF site
> of Zope.
> I have python-ldap module installed on a linux machine.
> My final intention is to Add an LDAP entry in to LDAP server.
> Following code i have written in a python script  just to get 
> started by
> connecting to LDAP server and accessing the existing contents.
>
> Script starts:
>
> import ldap
>
> ldapCon = ldap.open("localhost")
>
> ldapCon.simple_bind_s("cn=Manager,o=Lambent","secret");
>
> print 
> ldapCon.search_s("ou=HR,o=Lambent",ldap.SCOPE_SUBTREE,"objectclass=*")
>
> return printed
>
> Script ends.
>
> I am clueless as to what is causing this problem.
>
> Following error i have encountered :
>
>
> An error was encountered while publishing this resource.
>
> Error Type: Unauthorized
> Error Value: You are not allowed to access open in this context
>
>
>
> Troubleshooting Suggestions
>
> The URL may be incorrect.
> The parameters passed to this resource may be incorrect.
> A resource that this resource relies on may be encountering an error.
>
> For more detailed information about the error, please refer to the HTML
> source for this page.
>
> If the error persists please contact the site maintainer. Thank you 
> for your
> patience.
>
> Traceback (innermost last):
>   File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 
> 150, in
> publish_module
>   File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 
> 114, in
> publish
>   File /usr/local/Zope2.5.1/lib/python/Zope/__init__.py, line 159, in
> zpublisher_exception_hook
>     (Object: testsite)
>   File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 
> 98, in
> publish
>   File /usr/local/Zope2.5.1/lib/python/ZPublisher/mapply.py, line 
> 88, in
> mapply
>     (Object: ldap)
>   File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 
> 39, in
> call_object
>     (Object: ldap)
>   File 
> /usr/local/Zope2.5.1/lib/python/Shared/DC/Scripts/Bindings.py, line
> 252, in __call__
>     (Object: ldap)
>   File 
> /usr/local/Zope2.5.1/lib/python/Shared/DC/Scripts/Bindings.py, line
> 283, in _bindAndExec
>     (Object: ldap)
>   File
> /usr/local/Zope2.5.1/lib/python/Products/PythonScripts/PythonScript.py, 
> line
> 302, in _exec
>     (Object: ldap)
>     (Info: ({'script': <PythonScript instance at 8bbbeb0>, 'context':
> <CMFSite instance at 8b10098>, 'container': <CMFSite instance at 
> 8b10098>,
> 'traverse_subpath': []}, (), {}, None))
>   File Script (Python), line 7, in ldap
>   File /usr/local/Zope2.5.1/lib/python/AccessControl/ZopeGuards.py, 
> line 60,
> in guarded_getattr
>     (Object: ldap)
>   File 
> /usr/local/Zope2.5.1/lib/python/AccessControl/SecurityManager.py,
> line 83, in validate
>   File 
> /usr/local/Zope2.5.1/lib/python/AccessControl/ZopeSecurityPolicy.py,
> line 145, in validate
> Unauthorized: (see above)
>
>
> Plz reply ASAP,
>
> Regards
> Ashish.
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: Jabber - The world's fastest growing
> real-time communications platform! Don't just IM. Build it in!
> http://www.jabber.com/osdn/xim
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Accessing openLDAP Server from Python Script inside a Zope CMF.

[Ashish G. <As...@la...>]

Hi all,
I am trying to access openLDAP server from a python script inside CMF site
of Zope.
I have python-ldap module installed on a linux machine.
My final intention is to Add an LDAP entry in to LDAP server.
Following code i have written in a python script  just to get started by
connecting to LDAP server and accessing the existing contents.

Script starts:

import ldap

ldapCon = ldap.open("localhost")

ldapCon.simple_bind_s("cn=Manager,o=Lambent","secret");

print ldapCon.search_s("ou=HR,o=Lambent",ldap.SCOPE_SUBTREE,"objectclass=*")

return printed

Script ends.

I am clueless as to what is causing this problem.

Following error i have encountered :


An error was encountered while publishing this resource.

Error Type: Unauthorized
Error Value: You are not allowed to access open in this context



Troubleshooting Suggestions

The URL may be incorrect.
The parameters passed to this resource may be incorrect.
A resource that this resource relies on may be encountering an error.

For more detailed information about the error, please refer to the HTML
source for this page.

If the error persists please contact the site maintainer. Thank you for your
patience.

Traceback (innermost last):
  File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 150, in
publish_module
  File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 114, in
publish
  File /usr/local/Zope2.5.1/lib/python/Zope/__init__.py, line 159, in
zpublisher_exception_hook
    (Object: testsite)
  File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 98, in
publish
  File /usr/local/Zope2.5.1/lib/python/ZPublisher/mapply.py, line 88, in
mapply
    (Object: ldap)
  File /usr/local/Zope2.5.1/lib/python/ZPublisher/Publish.py, line 39, in
call_object
    (Object: ldap)
  File /usr/local/Zope2.5.1/lib/python/Shared/DC/Scripts/Bindings.py, line
252, in __call__
    (Object: ldap)
  File /usr/local/Zope2.5.1/lib/python/Shared/DC/Scripts/Bindings.py, line
283, in _bindAndExec
    (Object: ldap)
  File
/usr/local/Zope2.5.1/lib/python/Products/PythonScripts/PythonScript.py, line
302, in _exec
    (Object: ldap)
    (Info: ({'script': <PythonScript instance at 8bbbeb0>, 'context':
<CMFSite instance at 8b10098>, 'container': <CMFSite instance at 8b10098>,
'traverse_subpath': []}, (), {}, None))
  File Script (Python), line 7, in ldap
  File /usr/local/Zope2.5.1/lib/python/AccessControl/ZopeGuards.py, line 60,
in guarded_getattr
    (Object: ldap)
  File /usr/local/Zope2.5.1/lib/python/AccessControl/SecurityManager.py,
line 83, in validate
  File /usr/local/Zope2.5.1/lib/python/AccessControl/ZopeSecurityPolicy.py,
line 145, in validate
Unauthorized: (see above)


Plz reply ASAP,

Regards
Ashish.

Re: updating python from openLDAP

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

Ashish Gautam wrote:
 > i have python-ldap module installed too.
 > [..]
 > so if there are any API documentation and examples,plz let me
 > know.

http://python-ldap.sf.net/docs.shtml

Check out sub-directory Demo/ for examples of non-documented stuff.

Ciao, Michael.

Re: updating python from openLDAP

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

http://python-ldap.sourceforge.net/

On Monday, July 15, 2002, at 08:24 , Ashish Gautam wrote:

> Hello everybody,
> I have a runnning openLDAP server on linux.
> I want to write a module in python that will add entries to the openLDAP
> server.
> i have python-ldap module installed too.
> I just dont find any API documentation help and examples on this that will
> help me write the module.
> so if there are any API documentation and examples,plz let me know.
>
> Thanx in advance,
> Ashish.

updating python from openLDAP

[Ashish G. <As...@la...>]

Hello everybody,
I have a runnning openLDAP server on linux.
I want to write a module in python that will add entries to the openLDAP
server.
i have python-ldap module installed too.
I just dont find any API documentation help and examples on this that will
help me write the module.
so if there are any API documentation and examples,plz let me know.

Thanx in advance,
Ashish.

Re: FYI: Solved problems with NON-ASCII chars in DN when using OpenLDAP 2.1.x libs.

[Joe L. <jl...@op...>]

I've worked with the latest CVS code a bit. Hope to have more code to =
push it soon. I did note the new 2.1.3 update too, and saw the libldap_r =
build fix. Did you get a separate email from Kurt saying that it was =
going to be addressed in a 2.0.x release as well?


On Thursday, July 11, 2002, at 10:54 AM, Michael Str=F6der wrote:

> Michael Str=F6der wrote:
>> 1. Solve problems with NON-ASCII chars in DN when using OpenLDAP
>> 2.1.x libs.
>
> Now this turned out to be a problem with ldap.explode_dn() and =
errornous handling of NON-ASCII chars in DNs (e.g. for search root) in =
OpenLDAP servers 1.x and 2.0.x.
>
> Unlike former versions ldap_explode_dn() returns escaped values if the =
DN of OpenLDAP 2.1.x returns contains NON-ASCII chars. This is valid =
according to RFC2253 but causes compability problems with old OpenLDAP =
servers. The older OpenLDAP servers do not match the escaped values in =
DNs properly.
>
> See the following trace log of a situation hitting in web2ldap when =
accessing OpenLDAP 2.0.x (it works e.g. against Netscape Directory =
4.1x):
>
> *** _ldap.<built-in function explode_dn> (('cn=3DMichael
> =
>Str\xc3\xb6...@st...,ou=3DTesting,dc=3Dstroeder,dc=3D=
com',
> >0),{})
> >=3D> result: ['cn=3DMichael =
Str\\C3\\B6d...@st...',
> >'ou=3DTesting', 'dc=3Dstroeder', 'dc=3Dcom']
> >*** ldap.ldapobject.SimpleLDAPObject.search (('cn=3DMichael
> =
>Str\\C3\\B6d...@st...,ou=3DTesting,dc=3Dstroeder,dc=3D=
com',
> >0, '(objectclass=3D*)', ['cn'], 0),{})
> >=3D> result: 1
> >*** ldap.ldapobject.SimpleLDAPObject.result ((1, 1, -1),{})
> >=3D> LDAPError: {'info': '', 'matched':
> >'ou=3DTesting,dc=3Dstroeder,dc=3Dcom', 'desc': 'No such object'}
>
> Note also that ldap_explode_dn() is marked as deprecated in OpenLDAP =
2.1.x's ldap.h.
>
> Ciao, Michael.
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> PC Mods, Computing goodies, cases & more
> http://thinkgeek.com/sf
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

FYI: Solved problems with NON-ASCII chars in DN when using OpenLDAP 2.1.x libs.

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

Michael Str=F6der wrote:
>=20
> 1. Solve problems with NON-ASCII chars in DN when using OpenLDAP
> 2.1.x libs.

Now this turned out to be a problem with ldap.explode_dn() and=20
errornous handling of NON-ASCII chars in DNs (e.g. for search=20
root) in OpenLDAP servers 1.x and 2.0.x.

Unlike former versions ldap_explode_dn() returns escaped values if=20
the DN of OpenLDAP 2.1.x returns contains NON-ASCII chars. This is=20
valid according to RFC2253 but causes compability problems with=20
old OpenLDAP servers. The older OpenLDAP servers do not match the=20
escaped values in DNs properly.

See the following trace log of a situation hitting in web2ldap=20
when accessing OpenLDAP 2.0.x (it works e.g. against Netscape=20
Directory 4.1x):

*** _ldap.<built-in function explode_dn> (('cn=3DMichael
 >Str\xc3\xb6...@st...,ou=3DTesting,dc=3Dstroeder,d=
c=3Dcom',
 >0),{})
 >=3D> result: ['cn=3DMichael Str\\C3\\B6d...@st...'=
,
 >'ou=3DTesting', 'dc=3Dstroeder', 'dc=3Dcom']
 >*** ldap.ldapobject.SimpleLDAPObject.search (('cn=3DMichael
 >Str\\C3\\B6d...@st...,ou=3DTesting,dc=3Dstroeder,d=
c=3Dcom',
 >0, '(objectclass=3D*)', ['cn'], 0),{})
 >=3D> result: 1
 >*** ldap.ldapobject.SimpleLDAPObject.result ((1, 1, -1),{})
 >=3D> LDAPError: {'info': '', 'matched':
 >'ou=3DTesting,dc=3Dstroeder,dc=3Dcom', 'desc': 'No such object'}

Note also that ldap_explode_dn() is marked as deprecated in=20
OpenLDAP 2.1.x's ldap.h.

Ciao, Michael.

Re: #ifdef HAVE_SASL

[Hans A. <Han...@Ph...>]

On Donnerstag, 4. Juli 2002 20:01, Michael Ströder wrote:
> HI!
>
> For those who haven't built their local OpenLDAP libs with SASL
> support I have introduced #ifdef HAVE_SASL in setup.py and
> Modules/*.c.

That is good news...

> HAVE_SASL is automagically set according to the line libs in
> setup.cfg.
>
> It seems to work but please test!

Works for me.

> Ciao, Michael. (I really hate C!)

so do I,

Hans

--
Han...@Ph...

Re: Fat memory leaks

[Hans A. <Han...@Ph...>]

On Dienstag, 2. Juli 2002 12:58, Michael Ströder wrote:
> HI!
>
> I remember that someone reported memory leaks quite a while ago
> and there was no further action. Running some test scripts I can
> observe that the python-ldap using process grows quite fast.
>
> Does anybody have the time to look into this? If yes, please dig
> into Modules/LDAPObject.c, functions l_ldap_result() and
> l_ldap_search().
>
> Ciao, Michael.

Michael,

I did not have time to check for the mentioned memory leaks (you know,
 a baby at the age of three weeks simliy eats up all your spare time
 :-), but I found this in the ldapdns-FAQ (however, I have no idea if
 it is related...)

Q: i think ldapdns has a memory leak! it keeps growing!
A: the openldap client libraries seem to "cache" attributes, and on a
   heavy nameserver it may seem to grow for a while. make sure
 softlimit is correct, and that you have a backup nameserver. one day,
 i may write a more low-memory ldap client lib to fix this...
   [ or i may find a bug in my code... or YOU might. it's possible;
   especially since i refuse to look at code before 2am... ]

Hans

--
Han...@Ph...

Re: [Fwd: libldap_r: undefined symbol: ldap_first_reference (ITS#1922)]

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

Mauro Cicognini wrote:
> Michael Str=F6der wrote:
>=20
>> libs =3D ldap_r lber sasl
>>
>> BTW: Make sure to bring your CVS working tree in sync. There are some =

>> changes in there related to using libldap_r.
>>
>> Mauro, I'd be happy if you also test that on Win32.
>=20
> I'd be happy to do so; how do I proceed?
> Do I have to get everything from CVS?

Yes, please bring your working tree in sync.

Ciao, Michael.

Re: [Fwd: libldap_r: undefined symbol: ldap_first_reference (ITS#1922)]

[Mauro C. <mci...@si...>]

Michael Ströder wrote:

> HI!
>
> I filed a bug report for the problems with libldap_r:
>
>     http://www.OpenLDAP.org/its/index.cgi?findid=1922
>
> Credits go to Johannes Stezenbach for sorting that out.
>
> Now adding references.c and references.lo in 
> libraries/libldap_r/Makefile.in makes it possible to build with this 
> line in setup.cfg:
>
> libs = ldap_r lber sasl
>
> BTW: Make sure to bring your CVS working tree in sync. There are some 
> changes in there related to using libldap_r.
>
> Verify if everything works after installing:
>
> # python -c "import ldap"
>
> Under Linux you can check with ldd:
>
> # ldd /usr/lib/python2.2/site-packages/_ldap.so
>         libldap_r.so.2 => /usr/local/openldap2/lib/libldap_r.so.2 
> (0x4001f000)
>         liblber.so.2 => /usr/local/openldap2/lib/liblber.so.2 
> (0x40052000)
>         libsasl.so.7 => /usr/lib/libsasl.so.7 (0x4005e000)
>
> libldap.so.2 must not be mentioned there!
>
> Mauro, I'd be happy if you also test that on Win32.

I'd be happy to do so; how do I proceed?
Do I have to get everything from CVS?

FYI: ldaptor

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

HI!

There's a pure Python implementation of the LDAP protocol:

http://twistedmatrix.com/users/tv/ldaptor/

Looks nicely designed!

Maybe it's thread-safe...

Ciao, Michael.

Urgent issues (was: RedHat 8.0 RPMS -- what they foretell)

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

I forgot something. Several things to dig into:

0. At least test the CVS version!

1. Solve problems with NON-ASCII chars in DN when using OpenLDAP
2.1.x libs.

2. Find huge memory leaks reported to the list.

3. Dig into thread-safety issues with libldap_r. Despite your
personal conversation with Luke I have some doubts that this is
really solved.

4. Test build process with several flavors of OpenLDAP
(./configure --help to give you an idea).

5. Clean up the nightmare of DEFINE's used.

6. Find subtle problem with search continuations blocking the 
search in ldap.async when using the latest CVS versions.

Ciao, Michael.