From 5a8418a5400806fcd513b962372c0b8db9bde21a Mon Sep 17 00:00:00 2001 From: vanitasvitae Date: Thu, 15 Jun 2017 11:44:05 +0200 Subject: [PATCH] Add Proposal for Jingle Encrypted Transfers (jet) --- inbox/xep-jet.xml | 165 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 165 insertions(+) create mode 100644 inbox/xep-jet.xml diff --git a/inbox/xep-jet.xml b/inbox/xep-jet.xml new file mode 100644 index 00000000..2640381e --- /dev/null +++ b/inbox/xep-jet.xml @@ -0,0 +1,165 @@ + + +%ents; +]> + + +
+ Jingle Encrypted Transfers + This specification defines a method that allows file transfers via Jingle File Transfer to be end-to-end encrypted using established encryption schemes like OpenPGP or OMEMO. + &LEGALNOTICE; + XXXX + ProtoXEP + Standards Track + Standards + Council + + XEP-0234 + + + + jet + + jingle + http://xmpp.org/schemas/jingle.xsd + + + jingle:errors + http://xmpp.org/schemas/jingle-errors.xsd + + + jingle + + Paul + Schaub + vanitasvitae@riseup.net + vanitasvitae@jabberhead.tk + + + 0.0.1 + 2017-06-12 + vv +

First draft

 + +
+ +

&xep0234; has the disadvantage, that transmitted files are not encrypted (aside from regular TLS transport encryption), which means that intermediate nodes like the XMPP server(s) have access to the transferred data. Considering that end-to-end encryption becomes more and more important for communications, this is a major flaw that needs to be addressed.

+

This document defines a method to enable two communication partners to utilize an already established secure channel (eg. an OMEMO session) to exchange an encryption key which can then be used to encrypt/decrypt the offered/requested file.

+ + +

In order to initiate an encrypted file transfer, the initiator includes a key-element in the jingle-request. This key-element contains an encryption key which is used to encrypt/decryt the transferred key. In both file offers and file requests, it is the initiator, which dictates this key. The key is encrypted using the encryption method of the initiators choice. The initiator and responder must establish a session beforehand.

+ + +

In this scenario Romeo wants to send an encrypted text file over to Juliet. He chooses to use their existing OMEMO session to do so. First, he generates a fresh TODO-AES key and IV. This will later be used to encrypt and decrypt the file. In order to be transmitted, key and IV have to be serialized. Key and IV are both Base64 encoded and appended in the following form:

+ +

This text is encrypted using the established secure encryption method. The resulting OMEMO element is sent as part of the security element along with the rest of the jingle stanza over to Juliet.

+ + + + + + 1969-07-21T02:56:15Z + This is a test. If this were a real file... + text/plain + test.txt + + 6144 + w0mcJylzCn+AfvuGdqkty2+KP48= + + + + + + + +
+ BASE64ENCODED... + BASE64ENCODED... + BASE64ENCODED... +
+ BASE64-ENCODED-ENCRYPTED-KEY + + + + +]]> + +

Juliet decrypts the OMEMO element using her session with Romeo to retrieve the key and IV. Both Juliet and Romeo then carry on with the session negotiation as described in &xep0234;. Before Romeo starts transmitting the file, he encrypts it using the key and IV. He then transmitts the encrypted file over to Juliet.

+

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

+ + + +

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 him a key and IV which Romeo will use to encrypt the file before sending it to Juliet. In this example we assume, that Romeo and Juliet secured their communications using &xep0374;.

+ + + + + + w0mcJylzCn+AfvuGdqkty2+KP48= + + + + + + + + + + + + +]]> + + + + +

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:

+
    +
  • What cipher is used to encrypt the file? Examples would be AES-GCM128/256...
    • +
  • Cipher agility? What format is used to serialize key and IV?
    • +
  • How exactly are interrupted transfers resumed? How (long) are keys/IVs cached?
    • +
  • Is it in the scope of this approach to hide metadata?
    • +
  • How are transferred files authenticated? (See OMEMO audit)
    • +
  • May it be desirable to split data into chunks?
    • +
  • Please add to this list :)
    • +
+ +