XEP-XXXX: Jingle Encrypted Transports

Abstract:This specification defines a method that allows to use established encryption schemes like OpenPGP or OMEMO for end-to-end encryption of Jingle transports.
Author:Paul Schaub
Copyright:© 1999 – 2017 XMPP Standards Foundation. SEE LEGAL NOTICES.
Type:Standards Track
Last Updated:2017-06-12

WARNING: This document has not yet been accepted for consideration or approved in any official manner by the XMPP Standards Foundation, and this document is not yet an XMPP Extension Protocol (XEP). If this document is accepted as a XEP by the XMPP Council, it will be published at <http://xmpp.org/extensions/> and announced on the <standards@xmpp.org> mailing list.

Table of Contents

1. Introduction
2. Terminology
3. Principle
4. Encrypted Jingle File Transfer using JET
    4.1. File offer
    4.2. File Request
5. Ciphers
6. Security Considerations
7. Open Questions

    A: Document Information
    B: Author Information
    C: Legal Notices
    D: Relation to XMPP
    E: Discussion Venue
    F: Requirements Conformance
    G: Notes
    H: Revision History

1. Introduction

Jingle Encrypted Transports (JET) strives to provide a modular and easily extensible way to wrap Jingle Transports in an additional end-to-end encryption layer. The focus of this specification lays on being modular. It should be possible to extend existing Jingle use scenarios with end-to-end encryption by simply adding a JET element to the negotiation.

2. Terminology

JET uses multiple encryption layers, so it is necessary to declare a distinct denomination for the different keys involved.

Table 1: Denomination of keys used in the protocol

Designation Abbrevation Usage
Transport Key TK (Symmetric) key that is used to encrypt/decrypt the bytestreams sent/received through Jingle transports. This key encrypts the data two entities want to exchange. Examples for TK can be found under "Ciphers".
Initialization Vector IV Initialization vector that is used together with TK.
Transport Secret TS Serialization of TK and TI.
Envelope Element EE Output of an established end-to-end encryption methods when encrypting TS. Examples for such methods could be OMEMO Encryption (XEP-0384) [1] or OpenPGP for XMPP Instant Messaging (XEP-0374) [2].

3. Principle

Lets assume Romeo wants to initiate an encrypted Jingle session with Juliet. Prior to the Jingle session initiation, an already existing, established and (ideally) authenticated end-to-end encryption session between Romeo and Juliet MUST exist. Examples for suitable encryption sessions are OMEMO Encryption (XEP-0384) [1] and OpenPGP for XMPP Instant Messaging (XEP-0374) [2]. This session is needed to transfer the Transport Secret from Romeo to Juliet.

When this precondition is met, Romeo initially generates a transport key (TK) and associated initialization vector (IV). These will later be used by the sender to encrypt, and respectively by the recipient to decrypt data that is exchanged. This protocol defines a set of usable ciphers from which Romeo might choose. TK and IV are serialized to create the transport secret (TS).

Next Romeo uses her established encryption session with Juliet to encrypt TS. The resulting envelope element (EE) will be part of the Jingle session initiation as child of the JET <secret/> element.

When Juliet receives Romeos session request, she decrypts EE to retrieve TS, from which she can deserialize TK and IV. Now she and Romeo can go on with the session negotiation. Once the session is established, data can be encrypted and exchanged.

4. Encrypted Jingle File Transfer using JET

Jingle File Transfer (XEP-0234) [3] has the disadvantage, that transmitted files are not encrypted (aside from regular TLS transport encryption), which means that intermediate nodes like XMPP/proxy server(s) have access to the transferred data. Considering that end-to-end encryption becomes more and more important to protect free speech and personal expression, this is a major flaw that needs to be addressed.

In order to initiate an encrypted file transfer, the initiator includes a JET <secret/> in the Jingle file transfer request.

4.1 File offer

In this scenario Romeo wants to send an encrypted text file over to Juliet. He chooses to use their existing OMEMO Encryption (XEP-0384) [1] session to do so. First, he generates a fresh AES-256 transport key and IV. TK and IV are serialized into TS which is then encrypted using Romeos OMEMO session with Juliet.

The resulting OMEMO element (EE) is sent as part of the security element along with the rest of the jingle stanza over to Juliet.

Example 1. Romeo initiates an encrypted file offer

<iq from='romeo@montague.example/dr4hcr0st3lup4c'
  <jingle xmlns='urn:xmpp:jingle:1'
    <content creator='initiator' name='a-file-offer' senders='initiator'>
      <description xmlns='urn:xmpp:jingle:apps:file-transfer:5'>
          <desc>This is a test. If this were a real file...</desc>
          <hash xmlns='urn:xmpp:hashes:2'
      <transport xmlns='urn:xmpp:jingle:transports:s5b:1'
        <candidate cid='hft54dqy'
      <security xmlns='urn:xmpp:jingle:jet:0'
        <encrypted xmlns='urn:xmpp:omemo:0'>
          <header sid='27183'>
            <key rid='31415'>BASE64ENCODED...</key>
            <key rid='12321'>BASE64ENCODED...</key>

Juliet decrypts the OMEMO element (EE) using her session with Romeo to retrieve TS from which she deserializes TK and IV. Both Juliet and Romeo then carry on with the session negotiation as described in Jingle File Transfer (XEP-0234) [3]. Before Romeo starts transmitting the file, he encrypts it using TK and IV. He then transmitts the encrypted file over to Juliet.

When Juliet received the file, she uses the TK and IV to decrypt the received file.

4.2 File Request

Juliet might want to request a file transfer from Romeo. This can be the case, when Romeo hosts the file. In order to do so, she sends generates TK and IV, creates TS from those and encrypts TS with an encryption method of her choice to get EE. TK and IV will be used by Romeo to encrypt the requested file before sending it to Juliet. In this example we assume, that Romeo and Juliet secured their communications using OpenPGP for XMPP Instant Messaging (XEP-0374) [2].

Example 2. Juliet initiates an encrypted file request

<iq from='juliet@capulet.example/yn0cl4bnw0yr3vym'
  <jingle xmlns='urn:xmpp:jingle:1'
    <content creator='initiator' name='a-file-request' senders='responder'>
      <description xmlns='urn:xmpp:jingle:apps:file-transfer:5'>
          <hash xmlns='urn:xmpp:hashes:2'
      <transport xmlns='urn:xmpp:jingle:transports:s5b:1'
        <candidate cid='ht567dq'
      <security xmlns='urn:xmpp:jingle:jet:0'
        <signcrypt xmlns='urn:xmpp:openpgp:0'>
          <to jid='romeo@montague.example'/>
          <time stamp='2014-07-10T17:06:00+02:00'/>
            <body xmlns='jabber:client'>BASE64-ENCODED-ENCRYPTED-KEY</body>

5. Ciphers

In order to encrypt the transported bytestream, the initiator must transmit a cipher key to the responder. There are multiple options available:

Table 2: Available ciphers, configurations and their namespaces

Namespace Type Length (bits) Parameters Serialization
urn:xmpp:ciphers:aes-128-gcm-nopadding:0 AES 128 GCM/NoPadding 128BitKey::128BitIV
urn:xmpp:ciphers:aes-256-gcm-nopadding:0 AES 256 GCM/NoPadding 256BitKey::256BitIV

The column 'serialization' describes, how the key and iv are serialized. "::" means plain concatenation of byte arrays.

6. Security Considerations

The initiator SHOULD NOT use the generated key TK as IV, but instead generate a seperate random IV.

Instead of falling back to unencrypted transfer in case something goes wrong, implementations MUST instead abort the Jingle session, informing the user.

IMPORTANT: This approach does not deal with metadata. In case of Jingle File Transfer (XEP-0234) [3], an attacker with access to the sent stanzas can for example still see the name of the file and other information included in the <file/> element.

7. Open Questions

This is only a rough draft and there is still a ton of questions left to be answered. Here is a small non-exhaustive list of things I can think of:



Appendix A: Document Information

Series: XEP
Number: XXXX
Publisher: XMPP Standards Foundation
Status: ProtoXEP
Type: Standards Track
Version: 0.0.1
Last Updated: 2017-06-12
Approving Body: XMPP Council
Dependencies: XEP-0234
Supersedes: None
Superseded By: None
Short Name: jet
XML Schema for the 'jingle' namespace: <http://xmpp.org/schemas/jingle.xsd>
XML Schema for the 'jingle:errors' namespace: <http://xmpp.org/schemas/jingle-errors.xsd>
Registry: <http://xmpp.org/registrar/jet.html>
This document in other formats: XML  PDF

Appendix B: Author Information

Paul Schaub

Email: vanitasvitae@riseup.net
JabberID: vanitasvitae@jabberhead.tk

Appendix C: Legal Notices


This XMPP Extension Protocol is copyright © 1999 – 2017 by the XMPP Standards Foundation (XSF).


Permission is hereby granted, free of charge, to any person obtaining a copy of this specification (the "Specification"), to make use of the Specification without restriction, including without limitation the rights to implement the Specification in a software program, deploy the Specification in a network service, and copy, modify, merge, publish, translate, distribute, sublicense, or sell copies of the Specification, and to permit persons to whom the Specification is furnished to do so, subject to the condition that the foregoing copyright notice and this permission notice shall be included in all copies or substantial portions of the Specification. Unless separate permission is granted, modified works that are redistributed shall not contain misleading information regarding the authors, title, number, or publisher of the Specification, and shall not claim endorsement of the modified works by the authors, any organization or project to which the authors belong, or the XMPP Standards Foundation.

Disclaimer of Warranty

## NOTE WELL: This Specification is provided on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. ##

Limitation of Liability

In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall the XMPP Standards Foundation or any author of this Specification be liable for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising from, out of, or in connection with the Specification or the implementation, deployment, or other use of the Specification (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if the XMPP Standards Foundation or such author has been advised of the possibility of such damages.

IPR Conformance

This XMPP Extension Protocol has been contributed in full conformance with the XSF's Intellectual Property Rights Policy (a copy of which can be found at <https://xmpp.org/about/xsf/ipr-policy> or obtained by writing to XMPP Standards Foundation, P.O. Box 787, Parker, CO 80134 USA).

Appendix D: Relation to XMPP

The Extensible Messaging and Presence Protocol (XMPP) is defined in the XMPP Core (RFC 6120) and XMPP IM (RFC 6121) specifications contributed by the XMPP Standards Foundation to the Internet Standards Process, which is managed by the Internet Engineering Task Force in accordance with RFC 2026. Any protocol defined in this document has been developed outside the Internet Standards Process and is to be understood as an extension to XMPP rather than as an evolution, development, or modification of XMPP itself.

Appendix E: Discussion Venue

There exists a special venue for discussion related to the technology described in this document: the <jingle@xmpp.org> mailing list.

The primary venue for discussion of XMPP Extension Protocols is the <standards@xmpp.org> discussion list.

Discussion on other xmpp.org discussion lists might also be appropriate; see <http://xmpp.org/about/discuss.shtml> for a complete list.

Errata can be sent to <editor@xmpp.org>.

Appendix F: Requirements Conformance

The following requirements keywords as used in this document are to be interpreted as described in RFC 2119: "MUST", "SHALL", "REQUIRED"; "MUST NOT", "SHALL NOT"; "SHOULD", "RECOMMENDED"; "SHOULD NOT", "NOT RECOMMENDED"; "MAY", "OPTIONAL".

Appendix G: Notes

1. XEP-0384: OMEMO Encryption <https://xmpp.org/extensions/xep-0384.html>.

2. XEP-0374: OpenPGP for XMPP Instant Messaging <https://xmpp.org/extensions/xep-0374.html>.

3. XEP-0234: Jingle File Transfer <https://xmpp.org/extensions/xep-0234.html>.

Appendix H: Revision History

Note: Older versions of this specification might be available at http://xmpp.org/extensions/attic/

Version 0.0.1 (2017-06-12)

First draft