|
From: <jf...@se...> - 2001-10-22 18:07:12
|
Hello, I just installed OpenLDAP 2.0.17 and the CVS version of python-ldap, and am having the following error when trying to use it with Zope's LDAPAdpater: 2001-10-22T17:49:27 ERROR(200) Zope Could not import Products.LDAPAdapter Traceback (innermost last): File /usr/local/Zope-2.4.2/lib/python/OFS/Application.py, line 563, in import_product File /usr/local/Zope-2.4.2/lib/python/Products/LDAPAdapter/__init__.py, line 90, in ? File /usr/local/Zope-2.4.2/lib/python/Products/LDAPAdapter/LDAPAdapter.py, line 120, in ? File /usr/lib/python2.1/site-packages/ldap.py, line 2, in ? ImportError: /usr/lib/python2.1/site-packages/_ldap.so: undefined symbol: ldap_ufn_setfilter I know that that function exists in OpenLDAP, or at least is documented ... The site mentionned patches, where do I get those, if that's the problem? Thanks! J.F. |
|
From: Michael <mi...@st...> - 2001-10-22 18:22:26
|
jf...@se... wrote: > > > I just installed OpenLDAP 2.0.17 and the CVS version of python-ldap, See item 3 on http://python-ldap.sourceforge.net/faq.shtml Note that applying patches to python-ldap is experimental. Ciao, Michael. |
|
From: <jf...@se...> - 2001-10-22 20:57:45
|
Michael, I did see it, unfortunately, I'm not sure WHERE to find these patches, they don't seem to be in the CVS tree! Also, the README in the CVS says it was tested again OpenLDAP 2.0 and Python 2.0 ... Which is pretty damn close to what I'm using (Python 2.1.1 with OpenLDAP 2.0.17, although the files say 2.0.11 for some reason). Maybe I'll try the RPM's :) I just like hacking things myself! Thanks! J.F. On Mon, 22 Oct 2001, Michael [iso-8859-1] Str=F6der wrote: > jf...@se... wrote: > >=20 > >=20 > > I just installed OpenLDAP 2.0.17 and the CVS version of python-ldap, >=20 > See item 3 on http://python-ldap.sourceforge.net/faq.shtml >=20 > Note that applying patches to python-ldap is experimental. >=20 > Ciao, Michael. >=20 > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev >=20 |
|
From: Jean-François D. <jf...@me...> - 2001-10-23 03:15:22
|
Hello, OK, never mind, I eventually figured it out :) Turns out the patches are hidden inside the RPM's ! I had to do some manual work since I wanted it to work with Python 2.1, but now I'm not getting any errors ... I'm looking forward to trying it out :) Thanks for the contribution! Jean-François Doyon Carbon IT http://methane.org Tel.: (819) 827-9997 Fax : (819) 827-6653 -----Original Message----- From: pyt...@li... [mailto:pyt...@li...]On Behalf Of jf...@se... Sent: October 22, 2001 5:01 PM To: Michael Ströder Cc: pyt...@li... Subject: Re: Undefined Symbol? Michael, I did see it, unfortunately, I'm not sure WHERE to find these patches, they don't seem to be in the CVS tree! Also, the README in the CVS says it was tested again OpenLDAP 2.0 and Python 2.0 ... Which is pretty damn close to what I'm using (Python 2.1.1 with OpenLDAP 2.0.17, although the files say 2.0.11 for some reason). Maybe I'll try the RPM's :) I just like hacking things myself! Thanks! J.F. On Mon, 22 Oct 2001, Michael [iso-8859-1] Ströder wrote: > jf...@se... wrote: > > > > > > I just installed OpenLDAP 2.0.17 and the CVS version of python-ldap, > > See item 3 on http://python-ldap.sourceforge.net/faq.shtml > > Note that applying patches to python-ldap is experimental. > > Ciao, Michael. > > _______________________________________________ > Python-LDAP-dev mailing list > Pyt...@li... > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev > _______________________________________________ Python-LDAP-dev mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/python-ldap-dev |
|
From: <jf...@se...> - 2001-10-23 14:43:36
|
Hello,
I am now trying to get an SSL connection working with my OpenLDAP 2.0.11
slapd server, and have run into problems again :(
I run my slapd with "-h ldaps:///" so that it runs ONLY over SSL, this
means it listens on port 636.
Here's my bit of code:
server =3D ldap.open('myhost',636)
server.version =3D ldap.VERSION3
server.start_tls_s()
server.simple_bind_s("hidden","hidden")
And here's the result:
Traceback (most recent call last):
File "urds.py", line 5, in ?
server.start_tls_s()
ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
Here's what my slapd, with maximum logging (1), has to say about that:
Oct 23 10:38:57 grumbler slapd[5627]: connection_get(9): got connid=3D4=20
Oct 23 10:38:57 grumbler slapd[5627]: connection_read(9): checking for
input on id=3D4=20
Oct 23 10:38:57 grumbler slapd[5627]: connection_read(9): TLS accept error
error=3D-1 id=3D4, closing=20
Oct 23 10:38:57 grumbler slapd[5627]: connection_closing: readying conn=3D4
sd=3D9 for close=20
Oct 23 10:38:57 grumbler slapd[5627]: connection_close: conn=3D4 sd=3D9=20
Unfortunately, not very helpfull!
Any ideas? I successfully connect to this server using Perl and various
tools. I compiled my pyton-ldap from CVS and patched with all the patches
in the original "starttls" message from the list.
One thing: It would me nice ot have a central place where to get patches
and so on, took me a while to figure out where to get them, and even now,
I'm not allways sure which patch does what!
Thanks again!
J.F.
On Mon, 22 Oct 2001, Jean-Fran=E7ois Doyon wrote:
> Hello,
>=20
> OK, never mind, I eventually figured it out :) Turns out the patches are
> hidden inside the RPM's !
>=20
> I had to do some manual work since I wanted it to work with Python 2.1, b=
ut
> now I'm not getting any errors ...
>=20
> I'm looking forward to trying it out :)
>=20
> Thanks for the contribution!
>=20
> Jean-Fran=E7ois Doyon
> Carbon IT
> http://methane.org
> Tel.: (819) 827-9997
> Fax : (819) 827-6653
>=20
> -----Original Message-----
> From: pyt...@li...
> [mailto:pyt...@li...]On Behalf Of
> jf...@se...
> Sent: October 22, 2001 5:01 PM
> To: Michael Str=F6der
> Cc: pyt...@li...
> Subject: Re: Undefined Symbol?
>=20
> Michael,
>=20
> I did see it, unfortunately, I'm not sure WHERE to find these patches,
> they don't seem to be in the CVS tree! Also, the README in the CVS says i=
t
> was tested again OpenLDAP 2.0 and Python 2.0 ... Which is pretty damn
> close to what I'm using (Python 2.1.1 with OpenLDAP 2.0.17, although the
> files say 2.0.11 for some reason).
>=20
> Maybe I'll try the RPM's :) I just like hacking things myself!
>=20
> Thanks!
> J.F.
>=20
>=20
>=20
> On Mon, 22 Oct 2001, Michael [iso-8859-1] Str=F6der wrote:
>=20
> > jf...@se... wrote:
> > >
> > >
> > > I just installed OpenLDAP 2.0.17 and the CVS version of python-ldap,
> >
> > See item 3 on http://python-ldap.sourceforge.net/faq.shtml
> >
> > Note that applying patches to python-ldap is experimental.
> >
> > Ciao, Michael.
> >
> > _______________________________________________
> > Python-LDAP-dev mailing list
> > Pyt...@li...
> > https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
> >
>=20
>=20
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>=20
>=20
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>=20
|
|
From: Michael <mi...@st...> - 2001-10-25 13:01:26
|
jf...@se... wrote:
>
> server = ldap.open('myhost',636)
> server.version = ldap.VERSION3
> server.start_tls_s()
> server.simple_bind_s("hidden","hidden")
> [..]
> ldap.SERVER_DOWN: {'desc': "Can't contact LDAP server"}
Took me also a while to figure this one out. The CN attribute in the
server's certificate has to be EXACTLY the same like the host name
you're using when calling ldap.open(). Check that.
Note that since there's no certificate validation in place this
patch does not provide protection against MITM-attacks. It has
experimental status and shouldn't be used in a productive
environment.
Ciao, Michael.
|