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

Signed-off-by: Sumner Evans <sumner.evans@automattic.com>
pull/1830/head
Sumner Evans 2 years ago
parent 3fbb048689
commit d6c6a0361f
No known key found for this signature in database

@ -603,23 +603,26 @@ At any point the interactive verification can go wrong. The following describes
what to do when an error happens: what to do when an error happens:
- Alice or Bob can cancel the verification at any time. An - Alice or Bob can cancel the verification at any time. An
[`m.key.verification.cancel`](#mkeyverificationcancel) message must be sent to signify the [`m.key.verification.cancel`](#mkeyverificationcancel) message must be sent to
cancellation. signify the cancellation.
- The verification can time out. Clients should time out a verification that - The verification can time out. Clients should time out a verification that
does not complete within 10 minutes. Additionally, clients should expire a does not complete within 10 minutes. Additionally, clients should expire a
`transaction_id` which goes unused for 10 minutes after having last `transaction_id` which goes unused for 10 minutes after having last
sent/received it. The client should inform the user that the verification sent/received it. The client should inform the user that the verification
timed out, and send an appropriate `m.key.verification.cancel` message to timed out, and send an appropriate
the other device. [`m.key.verification.cancel`](#mkeyverificationcancel) message to the other
device.
- When the same device attempts to initiate multiple verification attempts, - When the same device attempts to initiate multiple verification attempts,
the recipient should cancel all attempts with that device. the recipient should cancel all attempts with that device.
- When a device receives an unknown `transaction_id`, it should send an - When a device receives an unknown `transaction_id`, it should send an
appropriate `m.key.verification.cancel` message to the other device appropriate [`m.key.verification.cancel`](#mkeyverificationcancel) message to
indicating as such. This does not apply for inbound the other device indicating as such. This does not apply for inbound
`m.key.verification.request` or `m.key.verification.cancel` messages. [`m.key.verification.request`](#mkeyverificationrequest),
- If the device receives a message out of sequence or that it was not [`m.key.verification.start`](#mkeyverificationstart), or
expecting, it should notify the other device with an appropriate [`m.key.verification.cancel`](#mkeyverificationcancel) messages.
`m.key.verification.cancel` message. - If the device receives a message out of sequence or that it was not expecting,
it should notify the other device with an appropriate
[`m.key.verification.cancel`](#mkeyverificationcancel) message.
##### Short Authentication String (SAS) verification ##### Short Authentication String (SAS) verification

Loading…
Cancel
Save