[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: ldapdb and cyrus-sasl 2.1.17



--On Sunday, January 25, 2004 1:12 PM +0100 Tony Earnshaw <tonye@billy.demon.nl> wrote:

søn, 25.01.2004 kl. 01.22 skrev Edward Rudd:

I am in the middle of upgrading my cyrus-sasl from 2.1.15 to 2.1.17
using the ldapdb auxprop plugin... And am having a major problem, where
whenever I try to authenticate with the imap server, the ldap
daemon(OpenLDAP 2.1.22) completely dies on me.. I even completely dumped
and recreated my entire LDAP database(slapcat/slapadd).  I have tested
the ldapdb from openldap p2.1.22 and openldap 2.1.25 and both yield the
same result..

All I can see from the logs (loglevel 255). Is it looks like sasl is not
sending the realm anymore.. The incoming bind DN is
uid=user,digest-md5,cn=auth instead of
uid=user,cn=realm,cn=digest-md5,cn=auth.. I am using e-mail style login
names.. (user@host.com)..


I placed a question on the Cyrus SASL list, asking whether people there
regard it as "safe" to replace 2.1.15 with 2.1.17. I gave my
environment, including Openldap. I'm still waiting for positive answers.
I'm also using libldapdb for Postfix snapshot - have to use the one from
2.1.22 with Openldap 2.2.5.


Tonni,

I upgraded to cyrus-sasl-2.1.17 without any noticeable difference in behavior. I use GSSAPI binds though.

--Quanah

--
Quanah Gibson-Mount
Principal Software Developer
ITSS/TSS/Computing Systems
ITSS/TSS/Infrastructure Operations
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html