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

Document the requirement that clients track the message_index

Browse source
This commit is contained in:
Mark Haines 2016-10-21 15:25:33 +01:00
parent 888e6a9f3b
commit 8641ef299e
1 changed files with 5 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
supporting-docs/guides/2016-10-18-e2e_implementation.rst
View file

@ -326,6 +326,11 @@ Encrypted events using this algorithm should have ``sender_key``,
Megolm session (see `below`__), the ciphertext can be Megolm session (see `below`__), the ciphertext can be
decrypted by passing the ciphertext into ``olm_group_decrypt``. decrypted by passing the ciphertext into ``olm_group_decrypt``.
In order to avoid replay attacks a client should remember the megolm
``message_index`` of each event they decrypt for each session. If the client
decrypts an event with the same ``message_index`` as one that it has already
decrypted using that session then it should fail decryption.
__ `m.room_key`_ __ `m.room_key`_
The client should check that the sender's fingerprint key matches the The client should check that the sender's fingerprint key matches the