Arthur de Jong <adej...@debian.org> writes: > Can you check out the SVN version and see if there are any things I > missed? Currently the tool completely replaces the debconf data every > time but I think this makes the logic as understandable as possible > for now.
The auto SASL mechanism need support in the code: nslcd: [8b4567] <group(all)> DEBUG: ldap_initialize(ldap://192.168.122.4) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_rebind_proc() nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_PROTOCOL_VERSION,3) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_DEREF,0) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_TIMELIMIT,0) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_TIMEOUT,0) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_NETWORK_TIMEOUT,0) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_REFERRALS,LDAP_OPT_ON) nslcd: [8b4567] <group(all)> DEBUG: ldap_set_option(LDAP_OPT_RESTART,LDAP_OPT_ON) nslcd: [8b4567] <group(all)> DEBUG: ldap_sasl_interactive_bind_s(NULL,"auto") (uri="ldap://192.168.122.4";) nslcd: [8b4567] <group(all)> failed to bind to LDAP server ldap://192.168.122.4: Unknown authentication method: Operation now in progress CRAM-MD5 need SASL SECPROPS minssf=0, I found it empirically, maybe a note about it could be usefull (in man page?) Regards. -- Daniel Dehennin Récupérer ma clef GPG: gpg --keyserver pgp.mit.edu --recv-keys 0x6A2540D1
pgpXdWi4HKW0n.pgp
Description: PGP signature
