From 64922771d4f5e7d46f5b8c42f2acb3ab70c2ed61 Mon Sep 17 00:00:00 2001 From: Hubert Chathi Date: Thu, 17 Nov 2022 02:27:40 -0500 Subject: [PATCH] Clarify that verifications without a request only happens over to-device (#1345) --- changelogs/client_server/newsfragments/1345.clarification | 1 + content/client-server-api/modules/end_to_end_encryption.md | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) create mode 100644 changelogs/client_server/newsfragments/1345.clarification diff --git a/changelogs/client_server/newsfragments/1345.clarification b/changelogs/client_server/newsfragments/1345.clarification new file mode 100644 index 00000000..8132e060 --- /dev/null +++ b/changelogs/client_server/newsfragments/1345.clarification @@ -0,0 +1 @@ +Clarify parts of the end-to-end encryption sections. diff --git a/content/client-server-api/modules/end_to_end_encryption.md b/content/client-server-api/modules/end_to_end_encryption.md index 78e1ef29..1cba8a22 100644 --- a/content/client-server-api/modules/end_to_end_encryption.md +++ b/content/client-server-api/modules/end_to_end_encryption.md @@ -551,7 +551,8 @@ then the device IDs should be compared instead. If the two method, then the verification should be cancelled with a `code` of `m.unexpected_message`. -An `m.key.verification.start` message can also be sent independently of any +When verifying using to-device messages, an `m.key.verification.start` +message can also be sent independently of any request, specifying the verification method to use. This behaviour is deprecated, and new clients should not begin verifications in this way. However, clients should handle such verifications started by other clients.