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

add from_device fields and a FIXME

Browse source
This commit is contained in:
Hubert Chathi 2019-10-08 16:19:39 -04:00
parent e19fca7d54
commit 7469198d8b
1 changed files with 7 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
proposals/2241-e2e-verification-in-dms.md
View file

@ -55,6 +55,8 @@ following properties in its contents:
they are named in this field. Users who are not named in this field and who they are named in this field. Users who are not named in this field and who
did not send this event should ignore all other events that have a did not send this event should ignore all other events that have a
`m.key.verification` relationship with this event. `m.key.verification` relationship with this event.
- `from_device`: Alice's device ID. This is required since some verification
methods may use the device IDs as part of the verification process.
Key verifications will be identified by the event ID of the key verification Key verifications will be identified by the event ID of the key verification
request event. request event.
@ -66,11 +68,16 @@ Clients should ignore verification requests that have been accepted or cancelled
To accept a key verification, Bob will send an `m.key.verification.start` event To accept a key verification, Bob will send an `m.key.verification.start` event
with the following properties in its contents: with the following properties in its contents:
TODO: MSC1849 may use `m.relationship` rather than `m.relates_to`, in which
case this proposal should follow suit.
- `m.relates_to`: an object with the properties: - `m.relates_to`: an object with the properties:
- `rel_type`: `m.reference` - `rel_type`: `m.reference`
- `event_id`: the event ID of the key verification request that is being - `event_id`: the event ID of the key verification request that is being
accepted accepted
- `method`: the key verification method that is being used - `method`: the key verification method that is being used
- `from_device`: Bob's device ID. This is required since some verification
methods may use the device IDs as part of the verification process.
Clients should ignore `m.key.verification.start` events that correspond to Clients should ignore `m.key.verification.start` events that correspond to
verification requests that it did not send. verification requests that it did not send.