Just upgraded openldap this morning from 2.2.13 -> 2.2.18, and rebuilt PAM
and pam-ldap .

Saslauthd now refuses to use pam-ldap, saying (snip of /var/log/authlog):

Nov 17 12:02:53 lb saslauthd[22716]: START: saslauthd 1.5.27
Nov 17 12:02:53 lb saslauthd[7078]: daemon started, listening on /var/run/sasl/mux
Nov 17 12:03:27 lb saslauthd[17251]: PAM adding faulty module: /usr/pkg/lib/security/pam_deny.so
Nov 17 12:03:27 lb saslauthd[17251]: PAM adding faulty module: /usr/pkg/lib/security/pam_warn.so
Nov 17 12:03:27 lb saslauthd[17251]: PAM adding faulty module: /usr/pkg/lib/security/pam_ldap.so
Nov 17 12:03:27 lb saslauthd[17251]: AUTHFAIL: username [PAM auth error]

Looks to me like it doesn't like a couple of builtins either - anyone have any idea why?

rasputin@lb:rasputin$ ldd  /usr/pkg/lib/security/pam_deny.so
/usr/pkg/lib/security/pam_deny.so:
        -lc.12 => /usr/lib/libc.so.12
rasputin@lb:rasputin$ ldd  /usr/pkg/lib/security/pam_warn.so
/usr/pkg/lib/security/pam_warn.so:
        -lc.12 => /usr/lib/libc.so.12
rasputin@lb:rasputin$ ldd  /usr/pkg/lib/security/pam_ldap.so 
/usr/pkg/lib/security/pam_ldap.so:
        -lpthread.0 => /usr/lib/libpthread.so.0
        -llber-2.2.7 => /usr/pkg/lib/liblber-2.2.so.7
        -lssl.3 => /usr/lib/libssl.so.3
        -lcrypto.2 => /usr/lib/libcrypto.so.2
        -lldap-2.2.7 => /usr/pkg/lib/libldap-2.2.so.7
        -lcrypt.0 => /usr/lib/libcrypt.so.0
        -lresolv.1 => /usr/lib/libresolv.so.1
        -lc.12 => /usr/lib/libc.so.12
        -lpam.0 => /usr/pkg/lib/libpam.so.0
rasputin@lb:rasputin$

I'm using the same config (ldap.conf) that I was three hours ago, so I don't think that's the
problem...
	

-- 
This must be Thursday. I never could get the hang of Thursdays. - Arthur Dent
Rasputin :: Jack of All Trades - Master of Nuns