6.0.0-alpha12
6/6/25

[#3235] IMP_IMAPClient:: and cram-md5 login failures
Summary IMP_IMAPClient:: and cram-md5 login failures
Queue IMP
Queue Version HEAD
Type Bug
State Resolved
Priority 3. High
Owners Horde Developers (at) , slusarz (at) horde (dot) org
Requester slusarz (at) horde (dot) org
Created 01/09/2006 (7088 days ago)
Due
Updated 02/03/2006 (7063 days ago)
Assigned 01/09/2006 (7088 days ago)
Resolved 02/03/2006 (7063 days ago)
Github Issue Link
Github Pull Request
Milestone 4.1.0
Patch No

History
02/03/2006 04:58:50 AM Michael Slusarz Comment #3
State ⇒ Resolved
Reply to this comment
Well... nobody has really complained too much about this.  Also, we 
now use Auth_SASL to formulate our responses so I feel much more 
secure using that code than our hacked code from other projects.  I'm 
going to close this with the understanding we will reopen if people 
are still experiencing issues (I never was in the first place).
01/09/2006 07:04:10 AM Michael Slusarz Comment #2 Reply to this comment
This should probably be considered a showstopper for 4.1.0.
01/09/2006 07:03:48 AM Michael Slusarz Comment #1
State ⇒ Assigned
Priority ⇒ 3. High
Type ⇒ Bug
Summary ⇒ IMP_IMAPClient:: and cram-md5 login failures
Queue ⇒ IMP
Assigned to Michael Slusarz
Assigned to Horde DevelopersHorde Developers
Reply to this comment
I have been receiving sporadic reports that cram-md5 authentication is 
not working.  I have personally tested this on my local server, and it 
works fine here.  But, see e.g.:



Dec 27 09:27:38 mamamia authdaemond: received auth request, 
service=imap, authtype=cram-md5

Dec 27 09:27:38 mamamia authdaemond: authldap: trying this module

Dec 27 09:27:38 mamamia authdaemond: cram: 
challenge=PDJDRUM2N0E3NURBMzFBOTc1MEQ0MUNENDkxREQxRTdBQG1hbWFtaWEudW5pY29uLm5ldD4=, 
response=dXNlcjEgNWI4OTIxYzQ0OTM5NTkxNTJkMzc4MGYyZmE1NjliZjc=

Dec 27 09:27:38 mamamia authdaemond: cram: decoded challenge/response, 
username 'user1'

Dec 27 09:27:38 mamamia authdaemond: using search filter: (uid=user1)

Dec 27 09:27:38 mamamia slapd[20864]: conn=9 op=3 SRCH 
base="dc=unicon,dc=net" scope=2 deref=0 filter="(uid=user1)"

Dec 27 09:27:38 mamamia slapd[20864]: conn=9 op=3 SRCH 
attr=destinationIndicator Maildir givenName  userPassword sn sn uid

Dec 27 09:27:38 mamamia slapd[20864]: <= bdb_equality_candidates: 
(uid) index_param failed (18)

Dec 27 09:27:38 mamamia slapd[20864]: conn=9 op=3 SEARCH RESULT 
tag=101 err=0 nentries=1 text=

Dec 27 09:27:38 mamamia authdaemond: one entry returned, DN: 
uid=user1,ou=users,o=sakai,dc=mamamia,dc=unicon,dc=net

Dec 27 09:27:38 mamamia authdaemond: raw ldap entry returned:

Dec 27 09:27:38 mamamia authdaemond: | givenName: Test User 1

Dec 27 09:27:38 mamamia authdaemond: | sn: 1

Dec 27 09:27:38 mamamia authdaemond: | userPassword: 
{SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g=

Dec 27 09:27:38 mamamia authdaemond: | uid: user1

Dec 27 09:27:38 mamamia imapd: LOGIN FAILED, method=CRAM-MD5, 
ip=[::ffff:10.15.18.110]

Dec 27 09:27:38 mamamia authdaemond: | destinationIndicator: /ldap/user1

Dec 27 09:27:38 mamamia authdaemond: authldaplib: sysusername=<null>, 
sysuserid=1, sysgroupid=1, homedir=/ldap/user1, address=user1, 
fullname=Test User 1, maildir=<null>, quota=<null>, options=<null>

Dec 27 09:27:38 mamamia authdaemond: authldaplib: clearpasswd=<null>, 
passwd={SHA}W6ph5Mm5Pz8GgiULbPgzG37mj9g=

Dec 27 09:27:38 mamamia authdaemond: authldap: REJECT - try next module

Dec 27 09:27:38 mamamia authdaemond: FAIL, all modules rejected

Dec 27 09:27:43 mamamia imapd: LOGOUT, ip=[::ffff:10.15.18.110]

Saved Queries