mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-24 18:22:24 -05:00
XEP-0384: fix namespace formatting
Signed-off-by: Maxime “pep” Buquet <pep@bouah.net>
This commit is contained in:
parent
309e76804f
commit
25fa261395
@ -493,7 +493,7 @@
|
|||||||
</section3>
|
</section3>
|
||||||
<section3 topic='Message structure description' anchor='message-structure-description'>
|
<section3 topic='Message structure description' anchor='message-structure-description'>
|
||||||
<p>
|
<p>
|
||||||
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.
|
An OMEMO encrypted message is specified to include an <encrypted> element in the <tt>&ns;</tt> 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.
|
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 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.
|
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.
|
The encrypted &content; element is encoded using base64 and placed as text content into the &payload; element.
|
||||||
|
Loading…
Reference in New Issue
Block a user