Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
E
evolution-data-server
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • evolution-data-server
  • Issues
  • #170

Closed
Open
Opened Oct 26, 2019 by David Hebbeker@dhebbeker

automatically obtain PGP keys for e-mail recipients via keyserver

Objective

Evolution should be able to automatically retrieve the PGP keys for the recipients from keyservers. This is apparently implemented by other clients as for example in Thunderbird with Enigmail.

This enables the user to encrypt messages to recipients without the necessity to manually check if a key is publicly available. The assessment of trust to the key is a separate issue.

Additional features

Ideally the following would be possible:

  • The search for keys would start in background as soon as a recipient is defined.
  • In case the result of the search is ambiguous, the user is prompted which key shall be used (remember decision).

Background information

This issue may be related to #39.

Reliance on auto-key-locate

It has been suggested by @mcrha that automatic key discovery with Evolution should be working solely by setting up GnuPG correctly. This would rely on libcamel invoking gpg configured to automatically locate and retrieve keys through auto-key-locate. It has been observed that Evolution 3.22.6 specifies the recipient in a form (<local@domain>), which is not used by auto-key-locate for lookups on a keyserver. This has been confirmed with GnuPG version 2.1.18, 2.2.12 and 2.2.17.

To this day it has not definitively been settled if this behavior of GnuPG is intended or not. This is quite uncertain as different parts (see auto-key-locate and user id) of the GnuPG manual are not necessarily consistent. It is at the discretion of the GnuPG developers if or when to change the accepted forms (see bug report).

Other approaches

Certainly other solutions should be possible. For example by altering the form when libcamel is adding the recipients to the argument list. As a workaround this script can be used to circumvent the interoperability issue.

A compelling solution implementing the additional features would probably require to have several different asynchronous calls to gpg.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/evolution-data-server#170