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

Client-Server and Server-Server specs disagree on default invite power level #1187

Closed
syldrathecat opened this issue Aug 1, 2022 · 7 comments · Fixed by #1371
Closed

Client-Server and Server-Server specs disagree on default invite power level #1187

syldrathecat opened this issue Aug 1, 2022 · 7 comments · Fixed by #1371
Labels
help wanted Interested in contributing to the spec? These would be great additions! spec-bug Something which is in the spec, but is wrong

Comments

@syldrathecat
Copy link

Link to problem area:

https://spec.matrix.org/v1.3/client-server-api/#mroompower_levels

The levels for kick, ban and redact default to 50 if they are not specified in the m.room.power_levels event, or if the room contains no m.room.power_levels event. invite defaults to 0 in either case.

https://spec.matrix.org/v1.3/server-server-api/#definitions

The levels given by the invite, kick, ban, and redact properties in the current m.room.power_levels state. Each defaults to 50 if unspecified.

Issue
With the change made in 136b5c9 to fix #860 / #1019, the client-server spec is now inconsistent with the default power levels specified in the server-server spec.

The server-server spec should be changed to also specify 0 as the default invite power level.

@syldrathecat syldrathecat added the spec-bug Something which is in the spec, but is wrong label Aug 1, 2022
@turt2live
Copy link
Member

at some point there was a security issue related to all of this, which isn't coming up in the flip-flopping history of the default power level.

That should be dug up and the history re-examined, I think.

@richvdh
Copy link
Member

richvdh commented Aug 2, 2022

I don't think there's any flip-flopping. The spec originally said the default level was 50, but Synapse never implemented that, and so the spec was changed in #1021 to match - except for this bit which seems to have been missed.

You might be thinking of matrix-org/synapse#6834, which changed the shape of the power_levels event that Synapse emits when it creates a room. But that's a different thing.

@richvdh richvdh added the help wanted Interested in contributing to the spec? These would be great additions! label Aug 2, 2022
@turt2live
Copy link
Member

I'm fairly certain there was an MSC about this, and an internal issue. Neither seem to be linked from the previous history :(

@richvdh
Copy link
Member

richvdh commented Aug 2, 2022

I don't believe there was an MSC, and the only internal issue I'm aware of is the one relating to matrix-org/synapse#6834.

@richvdh
Copy link
Member

richvdh commented Aug 2, 2022

@richvdh
Copy link
Member

richvdh commented Aug 2, 2022

@syldrathecat: thanks for reporting this! Would you mind opening a pull-request to fix it? It looks like the line that needs changing is in https://github.com/matrix-org/matrix-spec/blob/main/content/server-server-api.md.

@syldrathecat
Copy link
Author

syldrathecat commented Sep 2, 2022

@syldrathecat: thanks for reporting this! Would you mind opening a pull-request to fix it? It looks like the line that needs changing is in https://github.com/matrix-org/matrix-spec/blob/main/content/server-server-api.md.

I can't, sorry. The project does not accept pseudonymous contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Interested in contributing to the spec? These would be great additions! spec-bug Something which is in the spec, but is wrong
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants