We recently tried upgrading libpam-ldap on one of our mail servers here,
which triggered this bug (caused saslauthd to segfault on every
authentication attempt).  We originally tried a number of things to
resolve the issue since we didn't exactly know what was causing it, but
then found that rolling back libpam-ldap fixed it.  Some interesting
things that I noticed were that the local PAM authentication via LDAP
never broke during this; we were still able to log into multiple
accounts on the machine with the newer libpam-ldap, and also Dovecot
authentication via PAM was working fine - the only thing that broke was
saslauthd.  I'm thinking that the bug really could be in saslauthd and
not libpam_ldap, and might possibly be an old workaround in sasl's code
that broke with an API or behavior change in the newer libpam_ldap.

-- 
Ryan Thoryk
System Administrator
onShore Networks, LLC




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to