From e53e3ab01a8ab06184ecbce506bf5e920d661edf Mon Sep 17 00:00:00 2001 From: Richard van der Hoff Date: Mon, 24 Oct 2016 14:59:47 +0100 Subject: [PATCH] remove `unsigned` prop for verifying --- supporting-docs/guides/2016-10-18-e2e_implementation.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/supporting-docs/guides/2016-10-18-e2e_implementation.rst b/supporting-docs/guides/2016-10-18-e2e_implementation.rst index a018a4104..a754f7c64 100644 --- a/supporting-docs/guides/2016-10-18-e2e_implementation.rst +++ b/supporting-docs/guides/2016-10-18-e2e_implementation.rst @@ -671,8 +671,9 @@ This will return a result as follows: The client should first check the signatures on the signed key objects. As with checking the signatures on the device keys, it should remove the ``signatures`` -property, format the remainder as Canonical JSON, and pass the result into -``olm_ed25519_verify``, using the Ed25519 device key for the ``key`` parameter. +and (if present) ``unsigned`` properties, format the remainder as Canonical +JSON, and pass the result into ``olm_ed25519_verify``, using the Ed25519 device +key for the ``key`` parameter. Provided the key object passes verification, the client should then pass the key, along with the Curve25519 Identity key for the remote device, into