Merge pull request #414 from matrix-org/markjh/replays

Document the requirement that clients track the message_index
This commit is contained in:
Mark Haines 2016-10-21 16:52:52 +01:00 committed by GitHub
commit 8a99d531a9

View file

@ -328,6 +328,12 @@ decrypted by passing the ciphertext into ``olm_group_decrypt``.
__ `m.room_key`_ __ `m.room_key`_
In order to avoid replay attacks a client should remember the megolm
``message_index`` returned by ``olm_group_decrypt`` 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 received using that session then
it should treat the message as invalid.
The client should check that the sender's fingerprint key matches the The client should check that the sender's fingerprint key matches the
``keys.ed25519`` property of the event which established the Megolm session ``keys.ed25519`` property of the event which established the Megolm session
when `marking the event as verified`_. when `marking the event as verified`_.