Repository navigation
Conversation
Bcc recipients go to gpg as hidden recipients, so To and Cc cannot see whose keys were Bcc'd. A good signature from a key without the From address shows amber, not green. Encrypting to a key the keyring does not vouch for asks first in the composer, and each address is encrypted to the checked key by fingerprint, preferring a vouched one.
An account can now send its key in an Autocrypt header and keep the keys others send, gossip included, in a keyring of Hylki's own rather than the user's GnuPG keyring. Recipients are looked up by WKD while a message is addressed, each pill shows where its key comes from, and Encrypt turns on when everyone prefers it.
This was referenced Nov 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Builds on #595.
Autocrypt:header with a minimised key) and encrypt by default (prefer-encrypt=mutual). Incoming headers are read when an account has it on, withaddr=checked against From, and kept in a newpgp_peerstable. Keys go into Hylki's own GnuPG home (discovered-keys), never the user's keyring; the reader's one-click Autocrypt import now goes there too. The full recommendation algorithm (disable, discourage, available, encrypt), andAutocrypt-Gossipinside encrypted mail to several recipients.docs/OPENPGP_BACKEND.mdcompares GnuPG, Sequoia and RNP for RFC 9580, recommending Sequoia for the discovered-keys keyring first.Tests: header parse/emit, the recommendation table, peer-state updates, gossip filtering, WKD URLs and fallback with a fake network, and real-gpg tests that found keys stay out of the user's keyring and forged headers are refused. Not tested live: WKD against real servers.