[Tickets #10680] Re: Authentication via IMP does fail for some passwords while using IMAP directly does work

bugs at horde.org bugs at horde.org
Mon Nov 7 10:06:47 UTC 2011


BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/10680
------------------------------------------------------------------------------
  Ticket           | 10680
  Aktualisiert Von | tkrah at fachschaft.imn.htwk-leipzig.de
  Zusammenfassung  | Authentication via IMP does fail for some passwords while
                   | using IMAP directly does work
  Warteschlange    | Kronolith
  Version          | Git master
  Typ              | Bug
  Status           | Unconfirmed
  Priorität        | 2. Medium
  Milestone        |
  Patch            |
  Zuständige       |
------------------------------------------------------------------------------


tkrah at fachschaft.imn.htwk-leipzig.de (2011-11-07 10:06) hat geschrieben:

Debugged things but inserted the line 102, because the check:

if (!$imp_imap->ob)

is false.

The password is what i expect, but the raw imaplog does not show those  
password or the login command. The imap server does still deny  
authentication (and raw logs from dovecot) are showing "garbage" as  
password, not what the user entered above.

imap session output from horde:

S: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID  
ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready.
C: [SASL-IR AUTHENTICATE Command - username: horde-test at software-friends.de]
>>> Slow IMAP Command: 9,421 seconds
S: 1 NO [AUTHENTICATIONFAILED] Authentication failed.
C: [LOGIN Command - username: horde-test at software-friends.de]
>>> Slow IMAP Command: 14,181 seconds
S: 2 NO [AUTHENTICATIONFAILED] Authentication failed.

dovecot auth output:

MD5-CRYPT(;3<9A><CA><F1><B2>g:<FC><F1><F8>g<E3><FD><96>*) !=  
'$1$a0dd526a$POYliZyTPtYiz.FGbo.0H0'


So what dovecot does receive, is not what the user did entered (and is  
show from the horde:debug line). Any ideas where things may break?






More information about the bugs mailing list