On Sat, 2010-06-19 at 00:24 +0200, Daniel Dehennin wrote: > According to LDAP C API[1], mechanism can be NULL for LDAP_SASL_SIMPLE.
I can't find any relevant information in the RFC but I did find this: http://www.openldap.org/software/man.cgi?query=ldap_simple_bind_s which describes the ldap_sasl_interactive_bind_s() and ldap_sasl_bind_s() functions that are used (the latter is only used on old LDAP libraries so should probably be removed from nslcd). The mechanism may be NULL (or empty) to perform negotiation with the server on which mechanism to use. I doubt this works reliably in nslcd so I'm not too worried about it. I'd rather introduce an "auto" mechanism for this if it were really needed than to bring the use_sasl option back. -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong --
signature.asc
Description: This is a digitally signed message part
