From 3849495c3dba53f0e6b1c72880039ba8a2e7a906 Mon Sep 17 00:00:00 2001 From: Melvin Keskin Date: Thu, 12 Mar 2020 21:14:08 +0100 Subject: [PATCH] XEP-0384: Clarify confusing sentences --- xep-0384.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0384.xml b/xep-0384.xml index 72991b3e..24f0ce9f 100644 --- a/xep-0384.xml +++ b/xep-0384.xml @@ -481,8 +481,8 @@

An OMEMO encrypted message is specified to include an <encrypted> element in the 'urn:xmpp:omemo:1' namespace. It always contains two child nodes, the <header> and the &payload; element. The <header> element has an attribute named 'sid' referencing the device id of the sending device and contains one or multiple <keys> elements, each with an attribute 'jid' of one of the recipients bare JIDs as well as one or multiple <key> elements. - A <key> element has an attribute named 'rid' referencing the device id of the recipient device, and an attribute named 'kex' which defaults to 'false' and indicates if the enclosed encrypted message includes a key exchange. The ciphertext that is the key and HMAC encrypted using the long-standing OMEMO session for that recipient device is encoded using base64 and placed as text content into the <key> element. - The ciphertext that is the encrypted &content; element is encoded using base64 and placed as text content into the &payload; element. + A <key> element has an attribute named 'rid' referencing the device id of the recipient device, and an attribute named 'kex' which defaults to 'false' and indicates if the enclosed encrypted message includes a key exchange. The key and HMAC encrypted using the long-standing OMEMO session for that recipient device are encoded using base64 and placed as text content into the <key> element. + The encrypted &content; element is encoded using base64 and placed as text content into the &payload; element.