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

Merge pull request #3199 from uhoreg/deprecate_verification_start_spec

Browse Source 
Deprecate verifications that don't begin with a request.
pull/3214/head
Hubert Chathi 5 years ago committed by GitHub
parent 55c2866ef3 78adb21455
commit 701ca0f475
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File

1
changelogs/client_server/newsfragments/3199.deprecaation
Unescape Escape View File

@ -0,0 +1 @@
Deprecate starting verifications that don't start with `m.key.verification.request` as per [MSC3122](https://github.com/matrix-org/matrix-doc/pull/3122).

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

@ -528,7 +528,9 @@ method, then the verification should be cancelled with a `code` of
`m.unexpected_message`. `m.unexpected_message`.
An `m.key.verification.start` message can also be sent independently of any An `m.key.verification.start` message can also be sent independently of any
request, specifying the verification method to use. request, specifying the verification method to use. This behaviour is
deprecated, and new clients should not begin verifications in this way.
However, clients should handle such verifications started by other clients.
Individual verification methods may add additional steps, events, and Individual verification methods may add additional steps, events, and
properties to the verification messages. Event types for methods defined properties to the verification messages. Event types for methods defined

Write Preview
Loading…
Cancel
Save