From ba63bedec0fa0a83fcde7ea9597a3eeabe335df2 Mon Sep 17 00:00:00 2001 From: Patrick Cloke Date: Thu, 24 Jun 2021 08:32:36 -0400 Subject: [PATCH] Clarify that signature checks only apply to joining users. --- proposals/3083-restricted-rooms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/proposals/3083-restricted-rooms.md b/proposals/3083-restricted-rooms.md index 9adad0b62..63d290aa7 100644 --- a/proposals/3083-restricted-rooms.md +++ b/proposals/3083-restricted-rooms.md @@ -65,8 +65,8 @@ the `restricted` join rule has the same behavior as `public`, with the additiona caveat that servers must ensure that: * The user's previous membership was `invite` or `join`, or -* The `m.room.member` event has a valid signature from a homeserver whose users - have the power to issue invites. +* The `m.room.member` event with a `membership` of `join` has a valid signature + from a homeserver whose users have the power to issue invites. As normal, the above check is also performed against the current room state during [soft-failure](https://matrix.org/docs/spec/server_server/r0.1.4#soft-failure),