GNOME Bugzilla – Bug 205718
Import public keys from messages
Last modified: 2017-11-23 06:59:17 UTC
There needs to be some mechanism to search an email for a public key block and then import it to the user's local keyring. Similarly, there needs to be a mechanism to include a user's public key block in the message they're sending. Cut-and-pasting from a terminal window works, but is inconvenient. Crypto support will not be used, regrettably, unless it's extremely convenient.
I agree, but I've been putting this off because it's a royal pain in the buttox and not many people have asked for this feature (ie. you are the only one). I personally feel that this should probably share a lot of code with the S/MIME certificate manager code. Marking as future because I won't have time to do this for 1.0.
the backend code for this is now complete, just need a front-end (which would be like 5 lines of code if we didn't have to complicate it by adding a click-me button for the user to click if he/she wants to import it. *sigh*)
Does the mention of s/mime here mean that we will ever see s/mime support? This is a feature that is close to forcing me to use doze/outlook (yuk).
S/MIME will come one day, but not for a long time. When I said the backend code is now in place, I meant for PGP.
*** bug 270175 has been marked as a duplicate of this bug. ***
*** bug 209430 has been marked as a duplicate of this bug. ***
still missing in 2.1.4. hmm... could this be a desktop bounty?
Bumping version to a stable release.
This is very close to being completed now -- For S/MIME, when someone sends a signed message, even if the certificate is otherwise unknown, double-clicking on the certificate opens up a dialog showing X.509 cert details. however, there's nothing that can be done *from* that dialog box. I can't export the cert, and i can't import it into evolution's cert database (~/.pki/*.db). If you could make the dialog box slightly more featureful, i think you could close this 14-year-old ticket :)
I'm not a fan of auto-import, thus I added an "Import Certificate" button beside the "View Certificate" button in the signature details. The button is disabled when the same certificate had been found in the local certificate database (as reported by NSS). The function being used not necessarily returns the latest certificate, thus it can be inaccurate. Created commit 67d5a37 in evo master (3.25.3+)