MSC4499: Strict server signing key caching and key ID uniqueness#4499
Open
gamesguru wants to merge 1 commit into
Open
MSC4499: Strict server signing key caching and key ID uniqueness#4499gamesguru wants to merge 1 commit into
gamesguru wants to merge 1 commit into
Conversation
Signed-off-by: Shane Jaroch <chown_tee@proton.me>
turt2live
added
proposal
turt2live
reviewed
Jul 6, 2026
Member
There was a problem hiding this comment.
Implementation requirements:
- Server following guidance (backwards compatibility) - ideally multiple
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
2 participants
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.
Standardizes server signing key caching and introduces a First Seen Wins rule for key ID uniqueness.
Rendered
Implementations
Current (baseline Synapse) Complement results: (9 pass / 1 skip / 7 fail)
Current (continuwuity impl) Complement results: (10 pass / 0 skip / 4 fail)