From 47169fd74b1f8f76aa2464b586ee63c1b120582b Mon Sep 17 00:00:00 2001 From: Travis Ralston Date: Tue, 7 Jun 2022 17:11:27 -0600 Subject: [PATCH] Fix v9 redactions --- content/rooms/fragments/v9-redactions.md | 5 +++-- content/rooms/v9.md | 5 +---- 2 files changed, 4 insertions(+), 6 deletions(-) diff --git a/content/rooms/fragments/v9-redactions.md b/content/rooms/fragments/v9-redactions.md index 936a56d8..3247c59f 100644 --- a/content/rooms/fragments/v9-redactions.md +++ b/content/rooms/fragments/v9-redactions.md @@ -2,6 +2,9 @@ toc_hide: true --- +{{% added-in this=true %}} `m.room.member` events now keep `join_authorised_via_users_server` +in addition to other keys in `content` when being redacted. + {{% boxes/rationale %}} Without the `join_authorised_via_users_server` property, redacted join events can become invalid when verifying the auth chain of a given event, thus creating @@ -18,8 +21,6 @@ information. The full redaction algorithm follows. -{{% rver-fragment name="v3-handling-redactions" %}} - Upon receipt of a redaction event, the server must strip off any keys not in the following list: diff --git a/content/rooms/v9.md b/content/rooms/v9.md index 0bbaa42a..d4da72de 100644 --- a/content/rooms/v9.md +++ b/content/rooms/v9.md @@ -17,10 +17,7 @@ Clients which implement the redaction algorithm locally should refer to the ### Redactions -{{% added-in this=true %}} `m.room.member` events now keep `join_authorised_via_users_server` -in addition to other keys in `content` when being redacted. - -{{% rver-fragment name="v9-redactions" %}} +{{% rver-fragment name="v9-redactions" withVersioning="true" %}} ## Server implementation components