[KLUG Members] SASL

[Peter Buxton]

Hmm.... 'sasl_auxprop_plugin: sasldb' directly:

Dec 17 23:49:09 grimace cyrus/imapd[1559]: starttls: TLSv1 with cipher DES-CBC3-SHA (168/168 bits new) no authentication
Dec 17 23:49:12 grimace cyrus/imapd[1559]: login: localhost[127.0.0.1] peter DIGEST-MD5+TLS User logged in

That worked against /etc/sasldb2 with PLAIN turned off, but trying to
use 'saslauthd -a ldap' didn't until I created the deprecated
'/usr/etc/saslauthd.conf':

ldap_servers: ldap://localhost:389
ldap_search_base: dc=killdevil,dc=org
ldap_scope: sub


Dec 17 23:56:48 grimace cyrus/imapd[1646]: starttls: TLSv1 with cipher DES-CBC3-SHA (168/168 bits new) no authentication
Dec 17 23:56:51 grimace cyrus/imapd[1646]: login: localhost[127.0.0.1] peter plaintext+TLS

That works only with PLAIN set on.

Does it matter how LDAP or /etc/shadow stores the passwords? Should it
be MD-5, and do you have to specify that for either one? Or am I being a
butthead and should just pump PAM through LDAP? It seems silly to have a
working technology like MD-5 and not use it.

-- 
for gpg key: http://killdevil.org/~peter