Torsten Schlabach wrote:
Fabian Fagerholm wrote:
we need help from someone who can (has the ability to, and has the time to) read
the code and figure out what's happening here.
I decided to start investigating this, especially as the problem gets
worse with Exim -> Cyrus SASL -> ldapdb. Other then with that Cyrus
IMAPd -> Cyrus SASL -> ldapdb setup, the workaround to use a mechanism
!= DIGEST-MD5 between the ldapdb auxprop plugin and the LDAP server does
NOT work.
It will make sense to keep the people who make the SASL lib in the loop:
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3032
My current state of investigation is there as well. Unfortunately, not a
lot yet.
Regards,
Torsten
I've ran into SASL reentrant problems similar to this using the
GSSAPI mechanism from within ldapdb. In my case, it appeared to
be a problem in the openldap 2.1 sasl code.
After recompiling my ldapdb plugin using a more recent openldap
2.3 library my segfaults went away.
- Dan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
