wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Clarify soft-failure is extension of current algorithm.

Browse source 
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
Patrick Cloke 2021-06-24 08:30:49 -04:00 • committed by Richard van der Hoff
parent 3377d55c28
commit 2171d175e8
1 changed files with 4 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

9
proposals/3083-restricted-rooms.md
View file

@ -68,11 +68,10 @@ caveat that servers must ensure that:
* The `m.room.member` event has a valid signature from a homeserver whose users * The `m.room.member` event has a valid signature from a homeserver whose users
have the power to issue invites. have the power to issue invites.
The above check must also be performed against the current room state to potentially As normal, the above check is also performed against the current room state during
soft-fail the event. This is the primary mechanism for guarding against state [soft-failure](https://matrix.org/docs/spec/server_server/r0.1.4#soft-failure),
changes when old events are referenced. (E.g. if the power levels change, a to guard against servers issuing new membership events by referencing old
server should not be able to issue new membership events by referencing an old events in the room.
event in the room.)
Note that the homeservers whose users can issue invites are trusted to confirm Note that the homeservers whose users can issue invites are trusted to confirm
that the `allow` rules were properly checked (since this cannot easily be that the `allow` rules were properly checked (since this cannot easily be