diff --git a/content/rooms/fragments/v8-auth-rules.md b/content/rooms/fragments/v8-auth-rules.md index 3f1a4558..37dc729d 100644 --- a/content/rooms/fragments/v8-auth-rules.md +++ b/content/rooms/fragments/v8-auth-rules.md @@ -1,11 +1,9 @@ Events must be signed by the server denoted by the `sender` property. -`m.room.redaction` events are not explicitly part of the auth rules. -They are still subject to the minimum power level rules, but should always -fall into "10. Otherwise, allow". Instead of being authorized at the time -of receipt, they are authorized at a later stage: see the -[Redactions](#redactions) section below for more information. +While they are still subject to them, there are no auth rules specifically for +`m.room.redaction` events. The actual redaction of content is authorized at a +later stage: see the [Redactions](#redactions) section below for more information. The types of state events that affect authorization are: diff --git a/content/rooms/v10.md b/content/rooms/v10.md index 1d366c8c..5f70421d 100644 --- a/content/rooms/v10.md +++ b/content/rooms/v10.md @@ -76,11 +76,9 @@ correctly structured are rejected under the authorization rules below. Events must be signed by the server denoted by the `sender` property. -`m.room.redaction` events are not explicitly part of the auth rules. -They are still subject to the minimum power level rules, but should always -fall into "10. Otherwise, allow". Instead of being authorized at the time -of receipt, they are authorized at a later stage: see the -[Redactions](#redactions) section below for more information. +While they are still subject to them, there are no auth rules specifically for +`m.room.redaction` events. The actual redaction of content is authorized at a +later stage: see the [Redactions](#redactions) section below for more information. The types of state events that affect authorization are: diff --git a/content/rooms/v11.md b/content/rooms/v11.md index 5d44161c..4d0bf7fe 100644 --- a/content/rooms/v11.md +++ b/content/rooms/v11.md @@ -83,11 +83,9 @@ such events over the Client-Server API. Events must be signed by the server denoted by the `sender` property. -`m.room.redaction` events are not explicitly part of the auth rules. -They are still subject to the minimum power level rules, but should always -fall into "10. Otherwise, allow". Instead of being authorized at the time -of receipt, they are authorized at a later stage: see the -[Redactions](#redactions) section below for more information. +While they are still subject to them, there are no auth rules specifically for +`m.room.redaction` events. The actual redaction of content is authorized at a +later stage: see the [Redactions](#redactions) section below for more information. The types of state events that affect authorization are: diff --git a/content/rooms/v3.md b/content/rooms/v3.md index dd2fd144..b8134e0d 100644 --- a/content/rooms/v3.md +++ b/content/rooms/v3.md @@ -89,12 +89,10 @@ The complete structure of a event in a v3 room is shown below. ### Authorization rules -{{< added-in this=true >}} `m.room.redaction` events are no longer -explicitly part of the auth rules. They are still subject to the -minimum power level rules, but should always fall into "11. Otherwise, -allow". Instead of being authorized at the time of receipt, they are -authorized at a later stage: see the [Handling Redactions](#handling-redactions) -section below for more information. +{{< added-in this=true >}} While they are still subject to them, +there are no auth rules specifically for `m.room.redaction` events anymore. +The actual redaction of content is authorized at alater stage: see the +[Redactions](#redactions) section below for more information. {{< rver-fragment name="v3-auth-rules" withVersioning=true >}} diff --git a/content/rooms/v6.md b/content/rooms/v6.md index b0309254..c430abfd 100644 --- a/content/rooms/v6.md +++ b/content/rooms/v6.md @@ -40,11 +40,9 @@ in [room version 5](/rooms/v5). ### Authorization rules -`m.room.redaction` events are not explicitly part of the auth rules. -They are still subject to the minimum power level rules, but should always -fall into "10. Otherwise, allow". Instead of being authorized at the time -of receipt, they are authorized at a later stage: see the -[Handling Redactions](#handling-redactions) section below for more information. +While they are still subject to them, there are no auth rules specifically for +`m.room.redaction` events. The actual redaction of content is authorized at a +later stage: see the [Redactions](#redactions) section below for more information. {{< added-in this=true >}} Rule 4, which related specifically to events of type `m.room.aliases`, is removed. `m.room.aliases` events must still pass diff --git a/content/rooms/v7.md b/content/rooms/v7.md index eda351d0..defe90d4 100644 --- a/content/rooms/v7.md +++ b/content/rooms/v7.md @@ -37,11 +37,9 @@ new point for `membership=knock` is added. Events must be signed by the server denoted by the `sender` property. -`m.room.redaction` events are not explicitly part of the auth rules. -They are still subject to the minimum power level rules, but should always -fall into "10. Otherwise, allow". Instead of being authorized at the time -of receipt, they are authorized at a later stage: see the -[Redactions](#redactions) section below for more information. +While they are still subject to them, there are no auth rules specifically for +`m.room.redaction` events. The actual redaction of content is authorized at a +later stage: see the [Redactions](#redactions) section below for more information. The types of state events that affect authorization are: