From 857ff2573fb238ade39b054611e26842e8ea44c7 Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Sat, 18 Feb 2017 20:02:16 +0000 Subject: [PATCH] e2e guide: add link about m.room_key events. --- supporting-docs/guides/2016-10-18-e2e_implementation.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/supporting-docs/guides/2016-10-18-e2e_implementation.rst b/supporting-docs/guides/2016-10-18-e2e_implementation.rst index a754f7c64..d0e1ca5bd 100644 --- a/supporting-docs/guides/2016-10-18-e2e_implementation.rst +++ b/supporting-docs/guides/2016-10-18-e2e_implementation.rst @@ -396,7 +396,8 @@ These events contain key data to allow decryption of other messages. They are sent to specific devices, so they appear in the ``to_device`` section of the response to ``GET /_matrix/client/r0/sync``. They will also be encrypted, so will need decrypting as above before they can be -seen. +seen. (These events are generated by other clients - see `starting a megolm +session`_). The event content will contain an 'algorithm' property, indicating the encryption algorithm the key data is to be used for. Currently, this