[Tickets #13274] Re: Sporadic IMAP login errors

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13274
------------------------------------------------------------------------------
  Ticket             | 13274
  Updated By         | Thomas Jarosch <thomas.jarosch at intra2net.com>
  Summary            | Sporadic IMAP login errors
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Bug
  State              | Unconfirmed
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Thomas Jarosch <thomas.jarosch at intra2net.com> (2014-06-23 12:18) wrote:

Ok, so I was unable to trigger it again last week. I've re-enabled
the PLAIN auth mech in Socket.php as I didn't expect
it to be related to CRAM-MD5. Tadaaaa, it just happend.

Debug trace in IMAP_Client:
2014-06-24T10:38:30+02:00 NOTICE: HORDE [turba] TOMJ:  
setParam(password): foobar [pid 15671 on line 533 of "/datastore/D
2014-06-24T10:38:30+02:00 NOTICE: HORDE [turba] TOMJ:  
getParam(password) called [pid 15671 on line 488 of "/datastore/DEV
2014-06-24T10:38:30+02:00 NOTICE: HORDE [turba] TOMJ:  
getParam(password): foobar [pid 15671 on line 490 of "/datastore/D
2014-06-24T10:38:30+02:00 NOTICE: HORDE [turba] TOMJ:  
getParam(password) called [pid 15671 on line 488 of "/datastore/DEV
2014-06-24T10:38:30+02:00 NOTICE: HORDE [turba] TOMJ:  
getParam(password): foobar [pid 15671 on line 490 of "/datastore/D

2014-06-24T10:38:47+02:00 NOTICE: HORDE [turba] TOMJ:  
getParam(password) called [pid 17126 on line 488 of "/datastore/DEV
2014-06-24T10:38:47+02:00 NOTICE: HORDE [turba] TOMJ: getParam():  
password not set [pid 17126 on line 492 of "/datastore/
2014-06-24T10:38:47+02:00 ERR: HORDE [turba] No password provided.  
[pid 17126 on line 190 of "/datastore/DEVEL/framework/

Interesting to see that setParam(password) is never called for PID 17126.

I'm using a file based session handler so it was easy
to capture the content of the session file.

The odd part is, that the session stays "destroyed" even
when I use a different horde app (just modified the URL in the browser).

Wild guess: The encrypted password in the session data somehow get's  
corrupted.

I'll add verification code to Horde_Pack to test the result of pack()  
*inside* pack() again.
If it's not the same as the input, I'll log it. That might or might not
confirm #13275 for this issue.