GNOME Bugzilla – Bug 600445
Provide UI to manage mail server SSL/TLS certificates (camel-cert.db)
Last modified: 2014-04-14 00:47:06 UTC
Evolution has no UI to manage the mail server SSL/TLS certificates stored in ~/.evolution/camel-cert.db . If I want to reverse a previous decision to accept a certificate, I am left to excise the certificate from camel-cert.db using a hex editor. That's ridiculous. In general, the camel-cert.db system seems really weak. I would suggest dropping it and extending the system for mail user certificates (which is on the "Certificates" panel of the preferences and appears to use Mozilla PSM) to cover mail server certificates too.
See: http://mail.gnome.org/archives/evolution-list/2008-June/msg00088.html
*** Bug 606208 has been marked as a duplicate of this bug. ***
Created attachment 152617 [details] Screenshot of Evolution and PSM certificate managers (In reply to comment #0) > the system for mail user certificates (which is on > the "Certificates" panel of the preferences and appears to use Mozilla PSM) Upon closer inspection, the Evolution certificate manager doesn't actually use PSM; it is a separate implementation made to look like PSM (see the attached screenshot). That's silly. Evolution should use the standard certificate manager for GNOME (if there isn't one, there should be one). I may enter another bug to pursue this.
*** Bug 453233 has been marked as a duplicate of this bug. ***
Created attachment 243135 [details] Simple tool to edit camel-cert.db I ran into a problem with my camel-cert.db again today (I rejected a certificate permanently by mistake and had no way to change my decision) and wrote a simple tool to edit the file. I hope people find this useful in the absence of proper support in Evolution.
This is planned for Seahorse. Closing.
I just edited my camel-cert.db again: my mail server changed certificate and I wanted to remove the old one. Is there any evidence (e.g., a bug) of the plan to add the feature to Seahorse? If not, please reopen this bug.