From 6a5b66d2d8d802a770b6b7b4e44abd63d2d3d842 Mon Sep 17 00:00:00 2001 From: Mark Haines Date: Fri, 21 Oct 2016 15:48:44 +0100 Subject: [PATCH] Document the where the client gets the message index from --- supporting-docs/guides/2016-10-18-e2e_implementation.rst | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/supporting-docs/guides/2016-10-18-e2e_implementation.rst b/supporting-docs/guides/2016-10-18-e2e_implementation.rst index 164888ab5..a215e6d2d 100644 --- a/supporting-docs/guides/2016-10-18-e2e_implementation.rst +++ b/supporting-docs/guides/2016-10-18-e2e_implementation.rst @@ -327,9 +327,10 @@ Megolm session (see `below`__), the ciphertext can be 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. +``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 decrypted using that session then +it should fail decryption. __ `m.room_key`_