fix: Don't treat policy server signing keys as required for signature verification #2058
Labels
No labels
Abandoned
Blocked
Bug
Changelog
Added
Changelog
Missing
Changelog
None
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/E2EE
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Matrix/T&S
Merge
Merge/Manual
Merge/Squash
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
Support
bob the builder
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity!2058
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "nex/fix/skip-notary-ps-key"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I noticed my server kept asking notaries for the
ed25519:policy_serversigning key, which the spec says is not supposed to be queried as it's in the room state (and also not required for general signature verification). This PR just filters out that specific key.This will break servers that use the key ID
ed25519:policy_serveras their primary signing key ID but frankly if someone's doing that then that sounds like their problem.Pull request checklist:
mainbranch, and the branch is named something other thanmain.myself, if applicable. This includes ensuring code compiles.
Seems hacky but OK?
it is hacky but it fixes the problem now and gives me more time to finish refactoring the signing key system