On Tue, 30 Apr 2002, Eric S. Johansson wrote: > I understand that. What I can't figure out as how to get imapd to stop > insisting on cram-md5 from the local database
use the "mech_list" option (sasl_mech_list in imapd.conf), or just delete the plugins from your /usr/lib/sasl2 directory that you don't want. > OK, I deleted /etc/sasldb2 and now I get the log result down below. > As you'll see later, it still advertises cram-md5 as an authentication > capability even with the database gone. The above should fix that. > Apr 30 11:10:12 mail imapd[18739]: unable to open Berkeley db /etc/sasldb2: No such >file or directory > Apr 30 11:10:12 mail imapd[18739]: unable to open Berkeley db /etc/sasldb2: No such >file or directory > Apr 30 11:10:12 mail imapd[18739]: no secret in database > Apr 30 11:10:12 mail imapd[18739]: badlogin: relay.andrewandsons.com[192.168.255.1] >CRAM-MD5 [SASL(-13): user not found: no secret in database] > the log reports: > Apr 30 11:21:22 mail su(pam_unix)[18766]: session opened for user cyrus by >root(uid=0) > Apr 30 11:24:39 mail imapd[18761]: unknown password verifier saslauthd > Apr 30 11:24:39 mail imapd[18761]: badlogin: localhost.localdomain[127.0.0.1] >plaintex > t cyrus SASL(-4): no mechanism available: checkpass failed > Apr 30 11:26:02 mail su(pam_unix)[18766]: session closed for user cyrus > Apr 30 11:26:04 mail sshd(pam_unix)[2130]: session closed for user root > Apr 30 11:26:29 mail sshd(pam_unix)[18807]: session opened for user root by (uid=0) > > the fact I'm getting the unknown password verifier tells me that I I > have either a misspelling, I am missing a sasl2 authentication > library, or I didn't compile imapd correctly. saslauthd is a separate binary. you need to configure sasl --with-saslauthd to compile it (and enable the password verifier internal within the library). -Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 235 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
