Skip to content

MSC4416: Optionally requiring policy server signatures in a room#4416

Open
turt2live wants to merge 2 commits intomainfrom
travis/msc/policy-servers-room-version
Open

MSC4416: Optionally requiring policy server signatures in a room#4416
turt2live wants to merge 2 commits intomainfrom
travis/msc/policy-servers-room-version

Conversation

@turt2live
Copy link
Copy Markdown
Member

@turt2live turt2live commented Feb 6, 2026

Rendered

Disclosure: I am Director of Standards Development at The Matrix.org Foundation C.I.C., Matrix Spec Core Team (SCT) member, employed by Element, and operate the t2bot.io service. This proposal is written and published as a Trust & Safety team member allocated in full to the Foundation.


Depends on #4284


@turt2live turt2live changed the title MSC: Optionally requiring policy server signatures in a room MSC4416: Optionally requiring policy server signatures in a room Feb 6, 2026
@turt2live turt2live marked this pull request as ready for review February 6, 2026 00:42
@turt2live turt2live added requires-room-version An idea which will require a bump in room version proposal A matrix spec change proposal s2s Server-to-Server API (federation) room-spec Something to do with the room version specifications unassigned-room-version Remove this label when things get versioned. kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. safety labels Feb 6, 2026
@github-project-automation github-project-automation bot moved this to Tracking for review in Spec Core Team Workflow Feb 6, 2026
@turt2live turt2live moved this from Tracking for review to Ready for general review in Spec Core Team Workflow Feb 6, 2026
Copy link
Copy Markdown
Member Author

@turt2live turt2live Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Implementation requirements:

  • Unstable room version
  • Complement tests


To support the auth rule changes above, the auth events selection algorithm appends the following:

* Depending on the room version, the `m.room.policy` state event, if any.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If MSC4242 lands before this, then this isn't necessary.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does MSC4242 remove auth events selection?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind:core MSC which is critical to the protocol's success needs-implementation This MSC does not have a qualifying implementation for the SCT to review. The MSC cannot enter FCP. proposal A matrix spec change proposal requires-room-version An idea which will require a bump in room version room-spec Something to do with the room version specifications s2s Server-to-Server API (federation) safety unassigned-room-version Remove this label when things get versioned.

Projects

Status: Ready for general review

Development

Successfully merging this pull request may close these issues.

2 participants