[Standards] Encrypted Jingle File Transfer

Florian Schmaus flo at geekplace.eu
Tue Jun 6 15:32:03 UTC 2017

On 06.06.2017 17:11, Vanitas Vitae wrote:
>   * Implement the security element
>       o - leaves metadata in the clear
>       o + more flexible and easier to implement
>       o + integrates better into existing XEPs
>       o implementations that do not support this can still transfer the
>         (encrypted) file/stream (not sure, if this is positive/negative)

        o + is <description/> agnostic, can (theoretically) be used with
every already specified <description/> use case

>   * Transport metadata and key serialized/xmlenc encrypted
>       o + hides metadata
>       o - not trivial to do
>       o - more likely to require addon-XEPs

        o - requires extra <description/> per use-case

Both approaches require add-on XEPs.

- Florian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 642 bytes
Desc: OpenPGP digital signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20170606/41057778/attachment.sig>

More information about the Standards mailing list