GNOME Bugzilla – Bug 766275
Encrypt new message bodies and attachments using PGP/MIME
Last modified: 2021-07-05 13:26:21 UTC
When a user has a valid GPG key configured for their computer's local account, and all recipients have trusted PGP pubkeys, messages should be automatically encrypted using PGP/MIME on send. While some proper UX design needs to be done for this, per bug 766273 it should be possible to query the current account to obtain a public key if it exists. If so, then as the recipient list (To, CC & BCC) changes, the current recipients should be examined and if all have trusted GPG pubkeys then the message should be marked as to be encrypted. Similar to Bug 766274, perhaps a Gtk.InfoBar can be inserted to provide visual feedback about the encryption status and to allow the user to disable it for that message if needed, but that seems pretty intrusive for something that should happen all the time. When the user hits send, the message body and attachments should be encrypted and sent. 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.
Please also make sure, that drafts saved on the server during composition are encrypted automatically. (General GPG implementation seems to be taking place in #713403.)
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.