Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambiguity of rule 4.3.1 of the auth rules in room version 11 #2023

Closed
dkasak opened this issue Dec 4, 2024 · 0 comments · Fixed by #2024
Closed

Ambiguity of rule 4.3.1 of the auth rules in room version 11 #2023

dkasak opened this issue Dec 4, 2024 · 0 comments · Fixed by #2024
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit

Comments

@dkasak
Copy link
Member

dkasak commented Dec 4, 2024

Link to problem area: https://spec.matrix.org/v1.12/rooms/v11/#authorization-rules

Issue

Rule 4.3.1 states

[Changed in this version] If the only previous event is an m.room.create and the state_key is the sender, allow.

Which is a bit ambiguous: if the state_key is the sender of which event?

Previously it said

If the only previous event is an m.room.create and the state_key is the creator, allow.

So it's likely just a bad replacement as part of MSC2175.

@dkasak dkasak added the clarification An area where the expected behaviour is understood, but the spec could do with being more explicit label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification An area where the expected behaviour is understood, but the spec could do with being more explicit
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant