Filip/matrix-spec
1
0
Fork 0
mirror of https://github.com/matrix-org/matrix-spec synced 2026-03-17 00:44:09 +01:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity

Clarify that verifications without a request only happens over to-device (#1345)

Browse source
This commit is contained in:
Hubert Chathi 2022-11-17 02:27:40 -05:00 committed by GitHub
parent 1e393fbf92
commit 64922771d4
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
changelogs/client_server/newsfragments/1345.clarification Normal file
View file

@ -0,0 +1 @@
Clarify parts of the end-to-end encryption sections.

3
content/client-server-api/modules/end_to_end_encryption.md
View file

@ -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 method, then the verification should be cancelled with a `code` of
`m.unexpected_message`. `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 request, specifying the verification method to use. This behaviour is
deprecated, and new clients should not begin verifications in this way. deprecated, and new clients should not begin verifications in this way.
However, clients should handle such verifications started by other clients. However, clients should handle such verifications started by other clients.