GNOME Bugzilla – Bug 680205
Bad handling of broken certificates
Last modified: 2012-09-06 10:39:45 UTC
(Wondering if this hasn't been reported before...) After updating my mail server and accidentally creating new certificates I failed to connect to the server with Evolution while multiple things got wrong: * In the account management, trying to receive the possible login methods for TLS crashed * For SSL the same timed out After wondering for quite some time (and blaming the server configuration) I found that Evolution was stuck on the bad certificate or to be more precise on the mismatch between the saved certificate and the new one. After deleting .local/evolution/camel-cert.db everything worked fine again. Possible solution: Ask the user (with a big fat warning) whether the changed certificate is OK or not.
Thanks for a bug report. According to bug #266912 this should be fixed in 3.6.0+. I'm marking this as a duplicate of the older bug, but please update bug #266912 when you get to 3.6.0+ and this will not work. Thanks in advance. *** This bug has been marked as a duplicate of bug 266912 ***