After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 766277 - Decrypt messages encrypted as PGP/MIME or inline PGP
Decrypt messages encrypted as PGP/MIME or inline PGP
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: client+engine
master
Other Linux
: Normal enhancement
: ---
Assigned To: Geary Maintainers
Geary Maintainers
Depends on: 765516 766273
Blocks: 713403
 
 
Reported: 2016-05-11 13:59 UTC by Michael Gratton
Modified: 2021-07-05 13:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Michael Gratton 2016-05-11 13:59:08 UTC
When a user has a valid GPG key configured for their computer's local account (Bug 766273) and they receive a message that is encrypted either using PGP/MIME or as inline PGP, the message should be automatically decrypted.

Per the discussion in Bug 713403, there's a number of subtleties to be worked out, especially sounding full-text search, attachment handling and so on.

Right now, I'm favouring a just-in-time approach - decrypting the message when first viewed by the user and at that point, saving attachments, adding the message body to the FTS table, possibly writing the decrypted version to disk, and so on. This should probably be an automatic process when the message is first displayed for viewing, but since it may take some time it may need some additional "loading" indication in the UI. The user should be subtly notified when viewing a decrypted message, and warned in an obvious way that the message could not be decrypted if an error occurs during the process.

Note that the UI changes for this will be impacted by changes being made for Bug 765516 and will need to be coordinated with that work.
Comment 1 GNOME Infrastructure Team 2021-07-05 13:27:59 UTC
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
which have not seen updates for a longer time (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/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/geary/-/issues/

Thank you for your understanding and your help.