wholetrans/docs-matrix-spec
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

add links

Browse source
This commit is contained in:
Hubert Chathi 2022-10-12 16:32:00 -04:00
parent 76bf60a12f
commit f76ff36545
1 changed files with 7 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -436,20 +436,20 @@ In general, verification operates as follows:
- Alice requests a key verification with Bob by sending a key verification - Alice requests a key verification with Bob by sending a key verification
request event. If the verification is being requested in a room, this will request event. If the verification is being requested in a room, this will
be an event with type `m.room.message` and `msgtype` be an event with type [`m.room.message` and `msgtype:
`m.key.verification.request`; if the verification is being requested using m.key.verification.request`](#mroommessagemkeyverificationrequest); if the verification is being requested using
to-device messaging, this will be an event with type to-device messaging, this will be an event with type
`m.key.verification.request`. This event indicates the verification methods [`m.key.verification.request`](#mkeyverificationrequest). This event indicates the verification methods
that Alice's client supports. (Note that "Alice" and "Bob" may in fact be the that Alice's client supports. (Note that "Alice" and "Bob" may in fact be the
same user, in the case where a user is verifying their own devices.) same user, in the case where a user is verifying their own devices.)
- Bob's client prompts Bob to accept the key verification. When Bob accepts - Bob's client prompts Bob to accept the key verification. When Bob accepts
the verification, Bob's client sends an `m.key.verification.ready` event. the verification, Bob's client sends an [`m.key.verification.ready`](#mkeyverificationready) event.
This event indicates the verification methods, corresponding to the This event indicates the verification methods, corresponding to the
verification methods supported by Alice's client, that Bob's client supports. verification methods supported by Alice's client, that Bob's client supports.
- Alice's or Bob's devices allow their users to select one of the verification - Alice's or Bob's devices allow their users to select one of the verification
methods supported by both devices to use for verification. When Alice or Bob methods supported by both devices to use for verification. When Alice or Bob
selects a verification method, their device begins the verification by selects a verification method, their device begins the verification by
sending an `m.key.verification.start` event, indicating the selected sending an [`m.key.verification.start`](#mkeyverificationstart) event, indicating the selected
verification method. Note that if there is only one verification method in verification method. Note that if there is only one verification method in
common between the devices then the receiver's device (Bob) can auto-select common between the devices then the receiver's device (Bob) can auto-select
it. it.
@ -457,11 +457,11 @@ In general, verification operates as follows:
verification method. This could involve their clients exchanging messages, verification method. This could involve their clients exchanging messages,
Alice and Bob exchanging information out-of-band, and/or Alice and Bob Alice and Bob exchanging information out-of-band, and/or Alice and Bob
interacting with their devices. interacting with their devices.
- Alice's and Bob's clients send `m.key.verification.done` events to indicate - Alice's and Bob's clients send [`m.key.verification.done`](#mkeyverificationdone) events to indicate
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` event with a `code` field that indicates the reason [`m.key.verification.cancel`](#mkeyverificationcancel) event with a `code` field that indicates the reason
it was cancelled. it was cancelled.
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