Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2025-12-25 18:38:37 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Clarification regarding authorisation rules

Browse source 
The rules for m.room.power_levels power were somewhat unclear regarding the behaviour towards the always present keys, such as kick and ban. Additionally, it is now also clarified that in the users and events dictionary also added and removed keys are taken into consideration.
This commit is contained in:
Luca Becker 2019-07-16 17:33:13 +02:00 committed by GitHub
parent 7b0f5ea77b
commit 15994c61a5
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
specification/rooms/v1.rst
View file

@ -243,14 +243,15 @@ The rules are as follows:
#. If there is no previous ``m.room.power_levels`` event in the room, allow.
#. For each of the keys ``users_default``, ``events_default``,
``state_default``, ``ban``, ``redact``, ``kick``, ``invite``, as well as
each entry being changed under the ``events`` or ``users`` keys:
#. For the keys ``users_default``, ``events_default``,
``state_default``, ``ban``, ``redact``, ``kick``, ``invite`` check if they were changed.
For each of the changed keys, as well as
each entry being added, changed or removed under the ``events`` or ``users`` keys:
i. If the current value is higher than the ``sender``'s current power level,
i. If the current value is present and higher than the ``sender``'s current power level,
reject.
#. If the new value is higher than the ``sender``'s current power level,
#. If the new value is present and higher than the ``sender``'s current power level,
reject.
#. For each entry being changed under the ``users`` key, other than the