search for: db_ldap_search

Recently at Better.be we implemented LDAP authenticated bind support for dovecot. A patch against CVS HEAD is attached. I have not tested it against all possible configurations one can use, but the basic operation seems to be right. As documented in the patch, it adds one new option to the dovecot-ldap.conf configuration file: # Set "auth_bind" to "yes" if you want to use

...g file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the "ldap_lookup_pass" function (auth/passdb-ldap.c) just before loging the ldap request parameters (auth_request_log_debug) and to actually perform the search (db_ldap_search). The signal occurs on the call of t_strarray_join(attr_names, ",") What I'm observing is that the "attr_names" array of the "passdb_ldap_conn" ldap connection doesn't seem to hold the right attributes : while in the test62 version it holded 'uid' and...

...' type and since the 'db_ldap_init' function returns the existing ldap connection if it exists, the 'passdb_ldap_preinit' and 'usedb_ldap_preinit' will call the 'db_ldap_set_attrs' function on _the same_ 'ldap_connection' object. - So when the 'db_ldap_search' function is called from the 'passdb-ldap.c:ldap_lookup_pass function, the 5th argument (passdb_ldap_conn->attr_names) will point to the 'user_attrs' instead of the 'pass_attrs', since userdb_preinit will have already been called. - I've also noticed the use...

http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz http://dovecot.org/releases/dovecot-1.0.rc32.tar.gz.sig Pretty late for changes if v1.0 is supposed to come out tomorrow, but I can't really leave these LDAP bugs unfixed. They shouldn't anyway break anything, so here's one more day for you people to find out about any bugs. One thing that I'm a bit concerned about is the