Conversation
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
1 participant
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.
Adds draft FMSG-010 for client-side OpenPGP signing and encryption using the existing OpenPGP/MIME format. It fits the current fmsg message format without changes to the core specification, hashes, host behaviour, or client APIs.
The standard covers MIME packaging and attachments, key trust and verification, exposed metadata, and the limits of adding recipients to existing ciphertext. It also adds links in the standards index and site navigation.
Validation: the strict documentation build and local-link checks pass for all 16 generated HTML pages; both media-type examples parse correctly and fit the core 255-byte limit;
git diff --checkpasses.