python-ldap-dev — discussion among developers

Re: ldaps and Active Directory

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

Josh wrote:
>> Patrick A. Treptau wrote:
>>> I am pulling my hair out trying to connect via ldaps to one of our AD 
>>> controllers.
>>>
>>> host = "ldaps://ad_host:636"
>>
>> You should always use the fully-qualified which is in the CN of the server
>> certificate's subject DN.
> 
> Patrick isn't the only one running into the issue by the way, I see if appearing 
> for me as well. Windows 2008 server, getting ldap.SERVER_DOWN: {'info': 
> '(unknown error code)', 'desc': "Can't contact LDAP server"} When I try to 
> connect with ldaps:// to our host using it's FQDN.

As said try to debug with

openssl s_client -connect ad_host:636 -verify

(use -CApath or -CAfile options)

preferrably using the OpenSSL command-line tool linked to the same libs like
python-ldap.

Ciao, Michael.

Re: ldaps and Active Directory

[Josh <jo...@ro...>]

> Patrick A. Treptau wrote:
> > I am pulling my hair out trying to connect via ldaps to one of our AD 
> > controllers.
> > 
> > host = "ldaps://ad_host:636"
> 
> You should always use the fully-qualified which is in the CN of the server
> certificate's subject DN.

Patrick isn't the only one running into the issue by the way, I see if appearing 
for me as well. Windows 2008 server, getting ldap.SERVER_DOWN: {'info': 
'(unknown error code)', 'desc': "Can't contact LDAP server"} When I try to 
connect with ldaps:// to our host using it's FQDN.

Re: Non-ascii passwords

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

Marc Brevoort wrote:
> I've inherited a little authentication module which uses
> python-ldap (v1.92, 2005/11/03). For the most of it, it works
> fine, but when a user has decided to use non-ascii characters
> in their password, they will be blocked access and the
> authentication log shows a message such as:
> 
> 2010-08-27 11:02:50,398 DEBUG Exception: 'ascii' codec can't encode
> character u'\xdf' in position 5: ordinal not in range(128)

I'm not sure which component write this message.

But python-ldap expects all values to be raw strings. So the calling
application is responsible for converting Unicode objects to raw strings with
the appropriate encoding. In case of LDAPv3 this is UTF-8.

> - It should be possible to work around the issue by escaping the
> non-ascii characters in the password, replacing them with a backslash

Please try to understand first how the Python syntax representation of Unicode
and raw strings is which displayed in the message above.

http://docs.python.org/reference/lexical_analysis.html#string-literals

There's no need to mess with the back-slashes at all. Simply fix the calling
application to do the right thing. Probably calling password.encode('utf-8')
will do.

Ciao, Michael.

Non-ascii passwords

[Marc B. <kle...@ho...>]

Hello,

I've inherited a little authentication module which uses 
python-ldap (v1.92, 2005/11/03). For the most of it, it works 
fine, but when a user has decided to use non-ascii characters 
in their password, they will be blocked access and the 
authentication log shows a message such as:

2010-08-27 11:02:50,398 DEBUG Exception: 'ascii' codec can't encode character u'\xdf' in position 5: ordinal not in range(128)

As I'm not entirely comfortable yet working with Python, I'm
wondering if people here could advise on the best way to
resolve this issue. 

Some questions and doubts are: 
- is this a known problem that has been addressed in a later version? If so, would any compatibility issues be expected between the two
versions? 

- It should be possible to work around the issue by escaping the non-ascii characters in the password, replacing them with a backslash followed by one or more 2-digit hex codes representing the bytes that make up the character. Would it be necessary to do this in the python-ldap module, or would it be safe to do it before calling simple_bind?

Best regards,
Marc Brevoort


 		 	   		  

Re: Error to add objectClass to entries

[Steeve B. <ste...@gm...>]

I've found the solution. I use this method :

>>> mod_attrs = [( ldap.MOD_ADD, 'uidNumber', '1000' )]
>>> l.modify_s('uid=francis,ou=users,dc=example,dc=com', mod_attrs)

I had began with this method, but my error was to keep number as integer and
not as string.

Thx

Steeve Barbeau
http://steeve-barbeau.blogspot.com/
http://twitter.com/steevebarbeau



On Fri, Aug 20, 2010 at 10:27 AM, Chaos Eternal <cha...@gm...>wrote:

> you cannot alter/change stuctral objectClass of an existing entry
>
> On 20 Aug 2010 4:08 PM, "Steeve BARBEAU" <ste...@gm...> wrote:
>
> Hi,
>
> I'm new to this mailing list and I've a question concerning python-ldap.
> I want to add some objectClass and attributes to existing entries but I
> have this error :
> ldap.OTHER: {'info': 'no structuralObjectClass operational attribute',
> 'desc': 'Internal (implementation specific) error'}
>
> I'm using the add_s() function and I don't know if this is the good for
> doing that.
>
> PS : When I use the ldapmodify command with a ldif file and with the same
> attributes than in my python code, it works.
>
> You're help will be welcome, Thx
>
> Steeve Barbeau
> http://steeve-barbeau.blogspot.com/
> http://twitter.com/steevebarbeau
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Python-LDAP-dev mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-ldap-dev
>
>

Re: Error to add objectClass to entries

[Chaos E. <cha...@gm...>]

you cannot alter/change stuctral objectClass of an existing entry

On 20 Aug 2010 4:08 PM, "Steeve BARBEAU" <ste...@gm...> wrote:

Hi,

I'm new to this mailing list and I've a question concerning python-ldap.
I want to add some objectClass and attributes to existing entries but I have
this error :
ldap.OTHER: {'info': 'no structuralObjectClass operational attribute',
'desc': 'Internal (implementation specific) error'}

I'm using the add_s() function and I don't know if this is the good for
doing that.

PS : When I use the ldapmodify command with a ldif file and with the same
attributes than in my python code, it works.

You're help will be welcome, Thx

Steeve Barbeau
http://steeve-barbeau.blogspot.com/
http://twitter.com/steevebarbeau


------------------------------------------------------------------------------
This SF.net email is sponsored by

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Python-LDAP-dev mailing list
Pyt...@li...
https://lists.sourceforge.net/lists/listinfo/python-ldap-dev

Error to add objectClass to entries

[Steeve B. <ste...@gm...>]

Hi,

I'm new to this mailing list and I've a question concerning python-ldap.
I want to add some objectClass and attributes to existing entries but I have
this error :
ldap.OTHER: {'info': 'no structuralObjectClass operational attribute',
'desc': 'Internal (implementation specific) error'}

I'm using the add_s() function and I don't know if this is the good for
doing that.

PS : When I use the ldapmodify command with a ldif file and with the same
attributes than in my python code, it works.

You're help will be welcome, Thx

Steeve Barbeau
http://steeve-barbeau.blogspot.com/
http://twitter.com/steevebarbeau

Re: python-ldap-2.3.12: Compile error on CentOS 5.5, i386

[Zhang H. <zhb...@gm...>]

On Aug 12, 2010, at 2:42 AM, Michael Ströder wrote:
> 
> Looks like an older OpenLDAP release. Please try the patch below.
> 
> Ciao, Michael.
> 
> Index: Modules/constants.c
> ===================================================================
> RCS file: /cvsroot/python-ldap/python-ldap/Modules/constants.c,v
> retrieving revision 1.47
> diff -u -r1.47 constants.c
> --- Modules/constants.c	7 May 2010 13:22:40 -0000	1.47
> +++ Modules/constants.c	11 Aug 2010 05:14:47 -0000
> @@ -181,7 +181,9 @@
> #ifdef LDAP_OPT_X_TLS_CRLCHECK
>   /* only available if OpenSSL supports it => might cause backward
> compability problems */
> 	add_int(d,OPT_X_TLS_CRLCHECK);
> +#ifdef LDAP_OPT_X_TLS_CRLFILE
> 	add_int(d,OPT_X_TLS_CRLFILE);
> +#endif
> 	add_int(d,OPT_X_TLS_CRL_NONE);
> 	add_int(d,OPT_X_TLS_CRL_PEER);
> 	add_int(d,OPT_X_TLS_CRL_ALL);


This patch fixes it.
Will you release a 2.3.12.1 version for this fix?

Re: python-ldap-2.3.12: Compile error on CentOS 5.5, i386

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

Zhang Huangbin wrote:
> 
> On Aug 9, 2010, at 11:43 PM, Michael Ströder wrote:
> 
>> Find a new release of python-ldap:
>>
>>  http://pypi.python.org/pypi/python-ldap/2.3.12
> 
> Compile error on CentOS 5.5, i386:
> [..]
> Modules/constants.c: In function ‘LDAPinit_constants’:
> Modules/constants.c:184: error: ‘LDAP_OPT_X_TLS_CRLFILE’ undeclared (first use in this function)
> Modules/constants.c:184: error: (Each undeclared identifier is reported only once
> Modules/constants.c:184: error: for each function it appears in.)
> error: Setup script exited with error: command 'gcc' failed with exit status 1

Looks like an older OpenLDAP release. Please try the patch below.

Ciao, Michael.

Index: Modules/constants.c
===================================================================
RCS file: /cvsroot/python-ldap/python-ldap/Modules/constants.c,v
retrieving revision 1.47
diff -u -r1.47 constants.c
--- Modules/constants.c	7 May 2010 13:22:40 -0000	1.47
+++ Modules/constants.c	11 Aug 2010 05:14:47 -0000
@@ -181,7 +181,9 @@
 #ifdef LDAP_OPT_X_TLS_CRLCHECK
   /* only available if OpenSSL supports it => might cause backward
compability problems */
 	add_int(d,OPT_X_TLS_CRLCHECK);
+#ifdef LDAP_OPT_X_TLS_CRLFILE
 	add_int(d,OPT_X_TLS_CRLFILE);
+#endif
 	add_int(d,OPT_X_TLS_CRL_NONE);
 	add_int(d,OPT_X_TLS_CRL_PEER);
 	add_int(d,OPT_X_TLS_CRL_ALL);

python-ldap-2.3.12: Compile error on CentOS 5.5, i386

[Zhang H. <zhb...@gm...>]

On Aug 9, 2010, at 11:43 PM, Michael Ströder wrote:

> Find a new release of python-ldap:
> 
>  http://pypi.python.org/pypi/python-ldap/2.3.12

Compile error on CentOS 5.5, i386:

# easy_install python-ldap==2.3.12
Searching for python-ldap==2.3.12
Reading http://cheeseshop.python.org/pypi/python-ldap/
Reading http://www.python-ldap.org/
Reading http://cheeseshop.python.org/pypi/python-ldap/2.3.12
Best match: python-ldap 2.3.12
Downloading http://pypi.python.org/packages/source/p/python-ldap/python-ldap-2.3.12.tar.gz#md5=2dadc521b2c2590d9b033894ba5c6f31
Processing python-ldap-2.3.12.tar.gz
Running python-ldap-2.3.12/setup.py -q bdist_egg --dist-dir /tmp/easy_install-xqEjpH/python-ldap-2.3.12/egg-dist-tmp-AC0kEg
extra_compile_args: 
extra_objects: 
include_dirs: /usr/local/openldap-2.3/include /usr/include/sasl
library_dirs: /usr/local/openldap-2.3/lib
libs: ldap_r lber sasl2 ssl crypto
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
warning: no files found matching 'Makefile'
warning: no files found matching 'Modules/LICENSE'
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
file Lib/ldap.py (for module ldap) not found
file Lib/ldap/schema.py (for module ldap.schema) not found
Modules/constants.c: In function ‘LDAPinit_constants’:
Modules/constants.c:184: error: ‘LDAP_OPT_X_TLS_CRLFILE’ undeclared (first use in this function)
Modules/constants.c:184: error: (Each undeclared identifier is reported only once
Modules/constants.c:184: error: for each function it appears in.)
error: Setup script exited with error: command 'gcc' failed with exit status 1

ANN: python-ldap-2.3.12

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

Find a new release of python-ldap:

  http://pypi.python.org/pypi/python-ldap/2.3.12

python-ldap provides an object-oriented API to access LDAP directory
servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for
that purpose. Additionally it contains modules for other LDAP-related
stuff (e.g. processing LDIF, LDAPURLs and LDAPv3 schema).

Project's web site:

  http://www.python-ldap.org/

Ciao, Michael.

-- 
Michael Ströder
E-Mail: mi...@st...
http://www.stroeder.com

----------------------------------------------------------------
Released 2.3.12 2010-08-05

Changes since 2.3.11:

Lib/
* Removed tabs from various modules to make things work with python -tt.
* Quick fix to ldif.is_dn() to let multi-valued RDNs pass as valid.
  Is too liberal in some corner-cases though...
* Fix to ldif.is_dn() to allow dashes in attribute type (see SF#3020292)
* ldap.open() now outputs a deprecation warning
* module-wide locking is now limited to calling _ldap.initialize().
  Still ldap.functions._ldap_function_call() is used to wrap all
  calls for writing debug log.

Modules/
* New LDAP options available in OpenLDAP 2.4.18+ supported in
  LDAPObject.get/set_option():
  ldap.OPT_X_KEEPALIVE_IDLE, ldap.OPT_X_KEEPALIVE_PROBES,
  ldap.OPT_X_KEEPALIVE_INTERVAL,
  ldap.OPT_X_TLS_CRLCHECK, ldap.OPT_X_TLS_CRLFILE

Doc/
* Various small updates/improvements

Re: sasl bind issues

[Uma S. <um...@gm...>]

Yes that is correct. Using simple bind seems to have solved the problem
though..

2010/7/18 Michael Ströder <mi...@st...>

> Uma Sridharan wrote:
> >
> > Here is a sample code that works the first time I run the loop and fails
> > the second time with the following error. can someone let me know if the
> > credentials are cached by the library or what could be wrong? Any help
> > is greatly appreciated.
> >
> > ldap.INVALID_CREDENTIALS: {'info': '80090308: LdapErr: DSID-0C09043E,
> comment:
> > AcceptSecurityContext error, data 57, vece', 'desc': 'Invalid
> credentials'}
>
> Judging from the error message above I guess this is MS AD. Right?
>
> Somebody posted this issue with MS AD before. Frankly I have no clue what's
> going on and how to solve it. I could reproduce it with MS AD W2K3 but it
> works with other LDAP server implementations (tested with OpenLDAP 2.4.x
> and
> OpenDS 2.3beta).
>
> Ciao, Michael.
>

Active Directory - Security Descriptor

[Alex D. <ad...@gm...>]

Sorry if this is a noobish question (I am a noob when it comes to
Python-Ldap) but is it possible to retrieve the security descriptor for
objects? Such as a group?

I've googled around all day and read over the docs a hundred times and am
none the wiser. Is it possible?

Thanks for the help,
Alex

Re: sasl bind issues

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

Uma Sridharan wrote:
> 
> Here is a sample code that works the first time I run the loop and fails
> the second time with the following error. can someone let me know if the
> credentials are cached by the library or what could be wrong? Any help
> is greatly appreciated.
> 
> ldap.INVALID_CREDENTIALS: {'info': '80090308: LdapErr: DSID-0C09043E, comment: 
> AcceptSecurityContext error, data 57, vece', 'desc': 'Invalid credentials'}

Judging from the error message above I guess this is MS AD. Right?

Somebody posted this issue with MS AD before. Frankly I have no clue what's
going on and how to solve it. I could reproduce it with MS AD W2K3 but it
works with other LDAP server implementations (tested with OpenLDAP 2.4.x and
OpenDS 2.3beta).

Ciao, Michael.

sasl bind issues

[Uma S. <um...@gm...>]

Hi everyone,

Here is a sample code that works the first time I run the loop and fails the
second time with the following error. can someone let me know if the
credentials are cached by the library or what could be wrong? Any help is
greatly appreciated.

ldap.INVALID_CREDENTIALS: {'info': '80090308: LdapErr: DSID-0C09043E, comment:
AcceptSecurityContext error, data 57, vece', 'desc': 'Invalid credentials'}



import ldap, ldap.sasl


def main():
   while True:
        ldapServer="lserver"
        base ="ou=users,ou=accounts,dc=example,dc=com"
        user="user"
        passwd="pass"

        l = ldap.initialize(ldapServer)
        l.set_option(ldap.OPT_REFERRALS, 0)


        try:
            tok = ldap.sasl.digest_md5(user, passwd)
            l.sasl_interactive_bind_s("",tok)


        except ldap.INVALID_CREDENTIALS, e :

            print "Invalid Username or Password"
            print e
            return False
        print "success"
        l.unbind()



if __name__=="__main__":
     print "here"
     main()

sasl bind issues

[Uma S. <um...@gm...>]

Hi everyone,

Here is a sample code that works the first time I run the loop and fails the
second time with the following error. can someone let me know if the
credentials are cached by the library or what could be wrong? Any help is
greatly appreciated.

ldap.INVALID_CREDENTIALS: {'info': '80090308: LdapErr: DSID-0C09043E, comment:
AcceptSecurityContext error, data 57, vece', 'desc': 'Invalid credentials'}



import ldap, ldap.sasl


def main():
   while True:
        ldapServer="lserver"
        base ="ou=users,ou=accounts,dc=example,dc=com"
        user="user"
        passwd="pass"

        l = ldap.initialize(ldapServer)
        l.set_option(ldap.OPT_REFERRALS, 0)


        try:
            tok = ldap.sasl.digest_md5(user, passwd)
            l.sasl_interactive_bind_s("",tok)


        except ldap.INVALID_CREDENTIALS, e :

            print "Invalid Username or Password"
            print e
            return False
        print "success"
        l.unbind()



if __name__=="__main__":
     print "here"
     main()

Re: bad filter

[Anil <rep...@gm...>]

I've used this type of wild card search+compare before, all with
Solaris's ldapsearch, never complained. Let me change this to not use
a wild card like that.
Thanks.


2010/7/1 Michael Ströder <mi...@st...>:
> Anil wrote:
>> I pass a filter string such as this to search(), but I keep getting
>> BAD SEARCH FILTER error.
>> "(|(last-login-time<=100101*)(!(last-login-time=*)))"
>
> Using <= with * in the assertion value looks bogus to me.
>
>> The same thing works when using it with ldapsearch command.
>
> Does not work for me when using OpenLDAP's ldapsearch:
>
> $ ldapsearch "(|(last-login-time<=100101*)(\!(last-login-time=*)))"
> ldapsearch: ldap_search_ext: Bad search filter (-7)
>
> Note the extra back-shlash needed before ! since ! is a special char
> for the shell.
>
>> I also
>> tried running it through ldap.filter.escape_filter_chars.
>
> You should not pass complete filter strings to
> ldap.filter.escape_filter_chars(). This function should only be used for the
> assertion values you put into the filter string afterwards.
>
>> Is this a known bug?
>
> Nope.
>
> Ciao, Michael.
>

Re: bad filter

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

Anil wrote:
> I pass a filter string such as this to search(), but I keep getting
> BAD SEARCH FILTER error.
> "(|(last-login-time<=100101*)(!(last-login-time=*)))"

Using <= with * in the assertion value looks bogus to me.

> The same thing works when using it with ldapsearch command.

Does not work for me when using OpenLDAP's ldapsearch:

$ ldapsearch "(|(last-login-time<=100101*)(\!(last-login-time=*)))"
ldapsearch: ldap_search_ext: Bad search filter (-7)

Note the extra back-shlash needed before ! since ! is a special char
for the shell.

> I also
> tried running it through ldap.filter.escape_filter_chars.

You should not pass complete filter strings to
ldap.filter.escape_filter_chars(). This function should only be used for the
assertion values you put into the filter string afterwards.

> Is this a known bug?

Nope.

Ciao, Michael.

bad filter

[Anil <rep...@gm...>]

I pass a filter string such as this to search(), but I keep getting
BAD SEARCH FILTER error.
"(|(last-login-time<=100101*)(!(last-login-time=*)))"

The same thing works when using it with ldapsearch command. I also
tried running it through ldap.filter.escape_filter_chars. Still no
luck. Is this a known bug?
I am using python_ldap-2.3.8.

Thanks

Changed locking for function calls into _ldap

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

HI!

After Howard's answer

http://www.openldap.org/lists/openldap-software/201005/msg00054.html

I've relaxed the locking when calling functions of _ldap. Solely
_ldap.initialize() is now protected by a lock.

Also there's now debug logging for the locks if trace_level is 2 or higher.

Please review and test the code in HEAD especially with OpenLDAP 2.3 libs and
in heavily threaded environment.

Ciao, Michael.

Re: _ldap.so: undefined symbol: gnutls_alert_send

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

Jean-Sébastien Mansart wrote:
> 
> I've got this error with a Zope/Plone site :
> Traceback (most recent call last):
> [..]
> ImportError:
> /home/zope/z_sgec/buildout-cache/eggs/python_ldap-2.3.11-py2.4-linux-i686.egg/_ldap.so:
> undefined symbol: gnutls_alert_send
> 
> I have install gnutls1.3, recompiled openldap, python-ldap, and so on,
> but nothing works.

What does this command say?

ldd
/home/zope/z_sgec/buildout-cache/eggs/python_ldap-2.3.11-py2.4-linux-i686.egg/_ldap.so:

Note that there are various ways to install python-ldap:

1. Use pre-built packages from your Linux distributor.

2. Pre-built .egg-files which might be pulled in by dependencies of other
installed .egg files. (Personally I'm not in favour of this since most people
won't receive regular updates.)

3. Compile yourself and install. Which SSL/TLS libs are used (OpenSSL or
GNUtls) is determined by your OpenLDAP build.

For 1. and 2. you have to generally ask the distributor of the packages which
other software packages are needed. If you tried 1.,2. and 3. you have likely
a non-functional mixture of the above.

E.g. it seems your Zope/Plone installation (partially) pulls in a pre-built
.egg-file. My recommendation is to remove all occurences of python-ldap on
your system and try to cleanly do only one of the above.

For 3. you have to exactly use the Python interpreter your Zope/Plone
installation will run with.

Ciao, Michael.

_ldap.so: undefined symbol: gnutls_alert_send

[Jean-Sébastien M. <jea...@ba...>]

Hi.

I've got this error with a Zope/Plone site :
Traceback (most recent call last):
  File
"/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/run.py",
line 56, in ?
    run()
  File
"/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/run.py",
line 21, in run
    starter.prepare()
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/__init__.py",
line 102, in prepare
    self.startZope()
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/Startup/__init__.py",
line 278, in startZope
    Zope2.startup()
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/__init__.py",
line 47, in startup
    _startup()
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/Zope2/App/startup.py",
line 45, in startup
    OFS.Application.import_products()
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/OFS/Application.py",
line 686, in import_products
    import_product(product_dir, product_name, raise_exc=debug_mode)
  File
"/home/zope/z_sgec/Zope-2.10.11-final-py2.4/lib/python/OFS/Application.py",
line 709, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File
"/home/zope/z_sgec/buildout-cache/eggs/Products.LDAPMultiPlugins-1.9-py2.4.egg/Products/LDAPMultiPlugins/__init__.py",
line 22, in ?
    from Products.LDAPMultiPlugins.LDAPMultiPlugin import
addLDAPMultiPluginForm
  File
"/home/zope/z_sgec/buildout-cache/eggs/Products.LDAPMultiPlugins-1.9-py2.4.egg/Products/LDAPMultiPlugins/LDAPMultiPlugin.py",
line 29, in ?
    from Products.LDAPUserFolder import manage_addLDAPUserFolder
  File
"/home/zope/z_sgec/buildout-cache/eggs/Products.LDAPUserFolder-2.16-py2.4.egg/Products/LDAPUserFolder/__init__.py",
line 20, in ?
    from Products.LDAPUserFolder.LDAPUserFolder import LDAPUserFolder
  File
"/home/zope/z_sgec/buildout-cache/eggs/Products.LDAPUserFolder-2.16-py2.4.egg/Products/LDAPUserFolder/LDAPUserFolder.py",
line 47, in ?
    from Products.LDAPUserFolder.LDAPDelegate import filter_format
  File
"/home/zope/z_sgec/buildout-cache/eggs/Products.LDAPUserFolder-2.16-py2.4.egg/Products/LDAPUserFolder/LDAPDelegate.py",
line 19, in ?
    import ldap
  File
"/home/zope/z_sgec/buildout-cache/eggs/python_ldap-2.3.11-py2.4-linux-i686.egg/ldap/__init__.py",
line 22, in ?
    from _ldap import *
ImportError:
/home/zope/z_sgec/buildout-cache/eggs/python_ldap-2.3.11-py2.4-linux-i686.egg/_ldap.so:
undefined symbol: gnutls_alert_send

I have install gnutls1.3, recompiled openldap, python-ldap, and so on,
but nothing works.

Anyone could help me ?

Thanks.
-- 

*Jean-Sébastien Mansart *- Développeur Web
Email : jea...@ba...
<mailto:jea...@ba...>
Tel : 04 79 26 28 29

*Bayard Service Edition *
Savoie Technolac - House Boat
BP308 - 73377 Le Bourget du Lac Cedex
www.bayardserviceweb.com <http://www.bayardserviceweb.com>

-- 

*Jean-Sébastien Mansart *- Développeur Web
Email : jea...@ba...
<mailto:jea...@ba...>
Tel : 04 79 26 28 29

*Bayard Service Edition *
Savoie Technolac - House Boat
BP308 - 73377 Le Bourget du Lac Cedex
www.bayardserviceweb.com <http://www.bayardserviceweb.com>

Re: ldap.open() SSL patch

[Adam T. W. <awi...@op...>]

On Mon, 2010-04-19 at 12:12 -0300, ygo...@dc... wrote:
> Michael Ströder <mi...@st...>:
> > Just raising DeprecationWarning exception breaks existing code. I have to
> > reject your patch. ;-)
> I understand.
> > I've checked in a solution which only outputs a warning (just like  
> > md5.py does
> > in recent Python releases). So old code should still work.
> I agree that this is a better solution for now.
> BTW, python-ldap looks a little bit complicated to use. I wonder if it  
> has other functions just like ldap.open, making the API look more  
> complicated than it actually is. I think it would be nice for  
> python-ldap to have a major release with a simpler API.
> I'll write a smaller API on top of python-ldap to ease the most  
> frequent use cases (simple authentication, searching, etc). If you  
> like the idea, maybe we can work together on it.

As an LDAP admin for more than a decade.... this is nearly impossible to
do without loosing generality [especially authentication; and I expect
most applications implement an 'authentication' class anyway].

A search is a single method call, which seems pretty simple to me.

Perhaps you should look at the ldaphelper module created by Butcher.
<http://aleph-null.tv/article/20080125-1203-175.xml/ldaphelper%
3A-A-Python-Extension-Library-for-python-ldap>

It simplifies a few things, at minimal expense.

> PS: Sorry for the bad english.

Re: ldap.open() SSL patch

[<ygo...@dc...>]

Michael Ströder <mi...@st...>:

> Just raising DeprecationWarning exception breaks existing code. I have to
> reject your patch. ;-)

I understand.

> I've checked in a solution which only outputs a warning (just like  
> md5.py does
> in recent Python releases). So old code should still work.

I agree that this is a better solution for now.

BTW, python-ldap looks a little bit complicated to use. I wonder if it  
has other functions just like ldap.open, making the API look more  
complicated than it actually is. I think it would be nice for  
python-ldap to have a major release with a simpler API.

I'll write a smaller API on top of python-ldap to ease the most  
frequent use cases (simple authentication, searching, etc). If you  
like the idea, maybe we can work together on it.

Thank you!

PS: Sorry for the bad english.

-- 
Ygor Mutti (http://icaju.com - @Mamutti)

Re: ldap.open() SSL patch

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

ygo...@dc... wrote:
> Michael Ströder <mi...@st...>:
> 
>> Yes, you're right. I would accept such a patch. ;-)
>>
>> At least it's documented:
>>
>> http://www.python-ldap.org/doc/html/ldap.html#ldap.open
> 
> I was using ldap.open because there are many code samples where it's
> still used, in the tubes.
> 
> The new patch is attached.

Just raising DeprecationWarning exception breaks existing code. I have to
reject your patch. ;-)

I've checked in a solution which only outputs a warning (just like md5.py does
in recent Python releases). So old code should still work.

Ciao, Michael.