GNOME Bugzilla – Bug 356461
pgp/gnupg keyring integration
Last modified: 2021-05-19 11:46:49 UTC
Evolution got integrated into the gnome desktop for some good reasons, something that still is not integrated well is the way encryption keys are handled. Basic gnupg keyring features should be possible inside evolution, like adding public keys to persons in the adressbook and adjusting its trust level. There should be a separate column that show a icon for signed/encryted with colors for unknown status, good status, bad status. In the settings where you set the key-id, a drop down box containing the possible keys could be placed. Also a create key pair button and import key button is useful. I think encryption will be an important feature for professional users in the future. Thunderbird + enigmail is much easier to handle than evolution + seahorse due to the integration.
AFAIK, thunderbird + enigmail doesn't display if a key is available for the contact in the contact window. FYI, we need to get vCard 3 support and a stable libcryptui (from seahorse) before starting such work. could someone make it depend on the vCard 3 support bug #240756 ?
seahorse evolved, please review
Seahorse integration is proposed in Google SOC 2008. http://live.gnome.org/SummerOfCode2008/Ideas . Please keep track of that :)
What does "integration" mean exactly? Bug 508744 has been fixed; other bugs like bug 517576 are not fixed. It's hard to define a task as "done" or "resolved" without any clear criteria...
(In reply to André Klapper from comment #4) > What does "integration" mean exactly? Bug 508744 has been fixed; other bugs > like bug 517576 are not fixed. > > It's hard to define a task as "done" or "resolved" without any clear > criteria... From the original description: 1. Basic gnupg keyring features should be possible inside evolution, like adding public keys to persons in the adressbook and adjusting its trust level. 2. There should be a separate column that show a icon for signed/encryted with colors for unknown status, good status, bad status. 3. In the settings where you set the key-id, a drop down box containing the possible keys could be placed. 4. Also a create key pair button and import key button is useful. From these 2. is mostly fixed (different colour of the message header), 3. and 4. are probably not that critical. So, what really remains painfully missing is 1. (some integration with seahorse, so that finding missing certificate from keyserver, signing it, shouldn’t be done by copying signature IDs all over the place manually).
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/evolution/-/issues/ Thank you for your understanding and your help.