From 9627b0193cc353cae5c21a07d0eee2b5d73c1ca9 Mon Sep 17 00:00:00 2001 From: Daniel Gultsch Date: Tue, 26 Jan 2021 16:50:44 +0100 Subject: [PATCH] Retro-patch XEP-0454 fixed examples in OMEMO Media sharing --- xep-0454.xml | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/xep-0454.xml b/xep-0454.xml index f261795e..3e9c441f 100644 --- a/xep-0454.xml +++ b/xep-0454.xml @@ -33,6 +33,16 @@ XEP Editor (jsc) Accepted by vote of Council on 2021-01-13. + + 0.0.3 + 2021-01-21 + dg + +
    +
  • Fixed key length in examples
    • +
+ + 0.0.2 2021-01-10 @@ -66,15 +76,15 @@

To share the file the entity converts the HTTPS URL, the key and the IV to an aesgcm:// URL. Both IV and key are converted to their hex representation of 24 characters and 64 characters respectively and concatenated for a total of 88 characters (44 bytes). The IV comes first followed by the key. The resulting string is put in the anchor part of the aesgcm URL.

Note: HTTP Upload has transport encryption as a MUST. Non HTTPS URLs MUST not be converted to the aesgcm URL scheme.

The resulting aesgcm URL is encrypted as an OMEMO message and send to the recipient(s).

The sending entity MAY also generate a thumbnail as a JPEG data uri and include that in the same message. The aesgcm:// and the data:image/jpep, are seperated by a new line character. The message SHOULD NOT include anything else. The JPEG thumbnail SHOULD be kept small (approximately 5KiB) to not run into into stanza size limitations. As a result the resulting thumbnail is considered to only be a very blury, very rough representation of the image.

-