archive
/
matrix-spec
mirror of https://github.com/matrix-org/matrix-spec
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fixup! e2ee/device verification: move general error handling under framework

Browse Source 
Signed-off-by: Sumner Evans <sumner.evans@automattic.com>
pull/1830/head
Sumner Evans 2 years ago
parent d66a8057af
commit 55375f4452
No known key found for this signature in database
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File

6
content/client-server-api/modules/end_to_end_encryption.md
Unescape Escape View File

@ -471,8 +471,10 @@ In general, verification operates as follows:
that the verification was successful. that the verification was successful.
Verifications can be cancelled by either device at any time by sending an Verifications can be cancelled by either device at any time by sending an
[`m.key.verification.cancel`](#mkeyverificationcancel) event with a `code` field that indicates the reason [`m.key.verification.cancel`](#mkeyverificationcancel) event with a `code` field
it was cancelled. that indicates the reason it was cancelled. The
[Error handling during key verification](#error-handling-during-key-verification)
section explains specific situations where cancellation messages should be sent.
When using to-device messages, Alice may not know which of Bob's devices to When using to-device messages, Alice may not know which of Bob's devices to
verify, or may not want to choose a specific device. In this case, Alice will verify, or may not want to choose a specific device. In this case, Alice will

Write Preview
Loading…
Cancel
Save