Conversation
markmnl
force-pushed
the
feat/fmsg-008-signing
branch
from
September 12, 2026 06:04
b34b8d5 to
3f47129
Compare
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-008 for Ed25519 message signatures carried as an attachment, with canonical signing input, DNS key publication and signing policy, and verification of ordinary and add-to messages. Adds the standard to the index and site navigation.
The sending host stamps the send time before signing. Reactions remain incompatible with signing and have no exception to a required-signing policy. DNS records use DKIM tag-list and TXT-string parsing rules, with explicit handling of unusable records and a valid raw Ed25519 public-key example.
Validation:
git diff --checkpasses.