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

Signed-off-by: Sumner Evans <sumner.evans@automattic.com>
This commit is contained in:
Sumner Evans 2024-06-07 10:39:47 -06:00
parent d66a8057af
commit 55375f4452
No known key found for this signature in database

View file

@ -471,8 +471,10 @@ In general, verification operates as follows:
that the verification was successful.
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
it was cancelled.
[`m.key.verification.cancel`](#mkeyverificationcancel) event with a `code` field
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
verify, or may not want to choose a specific device. In this case, Alice will