GNOME Bugzilla – Bug 267253
changing from imap to imap+ssl works only after restart
Last modified: 2009-08-15 18:40:50 UTC
Please fill in this template when reporting a bug, unless you know what you are doing. Description of Problem: If you change the SSL settings of an imap account from "Never" to "Always" these settings are not used until restart of evolution. IMHO this is a security problem, because a user thinks he has a secure connection, but his password is transfered in plaintext. That's why I've changed the Priority to Critical. Steps to reproduce the problem: 1. configure an imap account, SSL: never 2. try to connect and use a wrong password (if you take care about your passwort ;-) ) 3. watch the network traffic with e.g. ethereal: protocol IMAP, password visible 4. change in the account settings use SSL to "Always" 5. try again to connect with a wrong password ;-) 6. you'll see in ethereal your password again - no SSL is used Actual Results: SSL is not used although it is configured Expected Results: SSL should be used if configured so How often does this happen? always when switching SSL from Never to Always Additional Information: after restarting evolution SSL is used
duplicate feature request (it has worked this way forever - some settings require a restart, others don't)
Hi, Sorry, but I don't understand why my arguments are completly ignored. If a user configures SSL than he expect SSL. He expect that his password is transfered encrypted. There is not hint that this setting requires a restart. Normally this is no so critical, but if his password is sent in plaintext over the net this is security critical. If you won't change the behaviour then please add a message box when this settings is changed. "These changes requires a restart of evolution. Until a restart you won't get a secure connection and you password is transfered in plaintext" So I ask you to reopen this bug. Thanks.
it was closed because it's a duplicate
Ok, after searching bugzilla I think this is a dupe of http://bugzilla.gnome.org/show_bug.cgi?id=207481 If this assumption is wrong, please tell me and add the correct bug number.