GNOME Bugzilla – Bug 556519
not saving password if server encryption is enabled
Last modified: 2009-12-22 12:42:34 UTC
Please describe the problem: evolution do not save the password if enabled ssl encruptuin and cram-md5 password. But it will save password if ssl and cram-md5 are disabled so after this session you can change the setting back to secure and the pass will stay saved. for more details you see bug report on ubuntu: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/255768 Steps to reproduce: 1. create new account with imap (a lest it is brocken with my imap) choise secure settincs ( i use ssl with cram-md5 ). you can use old account but you should remove pass for imap from seahorse. 2. check email... so it will as two times pass download email and on next session it will ask agene. Actual results: Expected results: Does this happen every time? Other information:
Please forward the relevant logs too.
I copy/past my comments from other bugreport. at the moment i do not have any more stable system to show the difference. And i do not like to provide complete log... it looks to mach not private for me. So here are interisting parts: --------------------- log ----------------------------------- Get folder info(0x1286360:mbox:/home/bex/.evolution/mail/local, '<null>')e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results) e-data-server-ui-Message: Key file does not have group 'Passwords-Mail' received: * OK GMX IMAP4 StreamProxy ready.^M sending : C00000 CAPABILITY^M received: * CAPABILITY IMAP4 IMAP4rev1 IDLE AUTH=LOGIN AUTH=CRAM-MD5^M received: C00000 OK CAPABILITY completed^M sending : A00001 AUTHENTICATE CRAM-MD5^M e-data-server-ui-Message: Unable to find password(s) in keyring (Keyring reports: No matching results) e-data-server-ui-Message: Key file does not have group 'Passwords-Mail' received: + MyEncryPtedPassWordTbdchne^M received: A00001 OK 23875046 logged in^M sending : A00002 LIST "" "*"^M ------------------------------------------------------- there is no password stored corresponding to this account. But there is stored smb password, so seems like seahorst working. After this part of log it begin listing and fethcing. And there is nothing about storing the password at all it the log. --------------------- log continue ---------------------------- received: * LIST () "/" "alex"^M received: * LIST () "/" "alex/bugtrack"^M ............. received: A00002 OK Completed^M sending : A00003 LSUB "" "*"^M received: * LSUB () "/" "alex"^M received: * LSUB () "/" "alex/bugtrack"^M ............... received: A00003 OK Completed^M sending : C00001 LOGIN xxx xxx^M received: C00001 OK 23875046 logged in^M sending : C00002 SELECT alex/bugtrack^M received: * FLAGS (\Answered \Flagged \Draft \Deleted \Seen)^M received: * OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen)]^M received: * 1977 EXISTS^M received: * 0 RECENT^M received: * OK [UIDVALIDITY 1101911864]^M received: * OK [UIDNEXT 15540]^M received: C00002 OK [READ-WRITE] Completed^M sending : C00003 UID FETCH 1:15539 (FLAGS)^M received: * 1 FETCH (UID 10427 FLAGS (\Flagged \Seen))^M received: * 2 FETCH (UID 10432 FLAGS (\Flagged \Seen))^M -------------------after this the is only fetching -----------------------------
are there any logfilter/parametrs to clean any privat information from this cind of logs.
This could be a duplicate of http://bugzilla.gnome.org/show_bug.cgi?id=552583
(In reply to comment #4) > This could be a duplicate of bug #552583 I believe it is (and it was a pretty famous bug). *** This bug has been marked as a duplicate of bug 552583 ***