Gary Mills
2004-01-07 20:28:08 UTC
I'm using SASL 2.1.15 CVS 2003-07-25 with Cyrus IMAP. I did a test
with Outlook Express 6 on Windows 2000 by selecting `secure password
authentication'. I was logged in with the correct account. OE6 kept
prompting me for my username and password, which I supplied. The IMAP
log looked like this:
Jan 4 19:27:11 electra imapd[26747]: [ID 824502 local6.notice] badlogin: [24.76.17.66] NTLM [SASL(-13): authentication failure: incorrect NTLM responses]
Jan 4 19:27:19 electra imapd[26747]: [ID 824502 local6.notice] badlogin: [24.76.17.66] NTLM [SASL(-13): authentication failure: incorrect NTLM responses]
This apparently means that my username or password was incorrect.
The code in ntlm.c seems to do the comparison correctly. Which secret
in sasldb2 is supposed to be used for this? I seem to have a whole
bunch: cmusaslsecretPLAIN cmusaslsecretDIGEST-MD5 cmusaslsecretCRAM-MD5
userPassword. Am I perhaps missing some configuration setting for NTLM?
SASL was built like this:
env LDFLAGS="-R/usr/local/lib" \
CC=cc \
./configure \
--localstatedir=/var/run \
--with-dblib=berkeley \
--with-bdb-libdir=/usr/local/src/db/db-3.1.17/build_unix \
--with-bdb-incdir=/usr/local/src/db/db-3.1.17/build_unix \
--with-saslauthd=/var/run/saslauthd \
--with-ipctype=doors \
--disable-checkapop \
--with-openssl=/usr/local/src/OpenSSL/openssl-0.9.6h \
--disable-otp \
--enable-login \
--enable-ntlm \
--disable-krb4 \
--disable-gssapi
It works for other mechanisms.
with Outlook Express 6 on Windows 2000 by selecting `secure password
authentication'. I was logged in with the correct account. OE6 kept
prompting me for my username and password, which I supplied. The IMAP
log looked like this:
Jan 4 19:27:11 electra imapd[26747]: [ID 824502 local6.notice] badlogin: [24.76.17.66] NTLM [SASL(-13): authentication failure: incorrect NTLM responses]
Jan 4 19:27:19 electra imapd[26747]: [ID 824502 local6.notice] badlogin: [24.76.17.66] NTLM [SASL(-13): authentication failure: incorrect NTLM responses]
This apparently means that my username or password was incorrect.
The code in ntlm.c seems to do the comparison correctly. Which secret
in sasldb2 is supposed to be used for this? I seem to have a whole
bunch: cmusaslsecretPLAIN cmusaslsecretDIGEST-MD5 cmusaslsecretCRAM-MD5
userPassword. Am I perhaps missing some configuration setting for NTLM?
SASL was built like this:
env LDFLAGS="-R/usr/local/lib" \
CC=cc \
./configure \
--localstatedir=/var/run \
--with-dblib=berkeley \
--with-bdb-libdir=/usr/local/src/db/db-3.1.17/build_unix \
--with-bdb-incdir=/usr/local/src/db/db-3.1.17/build_unix \
--with-saslauthd=/var/run/saslauthd \
--with-ipctype=doors \
--disable-checkapop \
--with-openssl=/usr/local/src/OpenSSL/openssl-0.9.6h \
--disable-otp \
--enable-login \
--enable-ntlm \
--disable-krb4 \
--disable-gssapi
It works for other mechanisms.
--
Gary Mills- -Unix Support- -U of M Academic Computing and Networking-
Gary Mills- -Unix Support- -U of M Academic Computing and Networking-