JEP-0116: Encrypted Sessions

Ian Paterson

Email: ian.paterson@clientside.co.uk
JID: ian@zoofy.com

Peter Saint-Andre

Email: stpeter@jabber.org
JID: stpeter@jabber.org

Dave Smith

Email: dizzyd@jabber.org
JID: dizzyd@jabber.org

1. Introduction

2. Dramatis Personae

3. Discovering Support

4. Online ESession Negotiation

4.1. ESession Request

4.2. Diffie-Hellman Preparation (Bob)

4.3. Generating Session Keys

4.4. Hiding Identity

4.5. ESession Response

4.6. Diffie-Hellman Preparation (Alice)

4.7. Verifying Bob's Identity

4.8. ESession Completion

5. Exchanging Stanzas

5.1. Encryptable Content

5.2. Encryption

5.3. Sending an Encrypted Stanza

5.4. Decryption

6. Re-Key Exchange

6.1. Re-Key Initiation

6.2. Re-Key Acceptance

6.3. Publishing Old MAC Values

7. ESession Termination

8. Signature Generation and Verification

8.1. XML Normalization

8.2. Hash

8.3. Generation

8.3.1. RSA

8.3.2. DSA

8.4. Signature Format

8.4.1. RSA

8.4.2. DSA

8.5. Verification

8.5.1. RSA

8.5.2. DSA

9. Security Considerations

9.1. Random Numbers

9.2. Re-Keying Limits

9.3. Verifying Keys

9.4. Replay Attacks

9.5. Unencrypted ESessions

9.6. Storage

9.7. Extra Responsabilities of Implementors

9.8. Mandatory to Implement Technologies

9.8.1. Block Cipher Algorithms

9.8.2. Key Signing Algorithms

9.8.3. Public Signature-Verification-Key Formats

9.8.4. Hash Algorithms

9.8.5. Compression Algorithms

10. IANA Considerations

11. Jabber Registrar Considerations

11.1. Namespaces

11.2. Field Standardization

12. XML Schemas

13. Open Issues

13.1. To Think About

13.2. To Do

Notes

Revision History

<iq type='get'
    from='alice@example.org/pda'
    to='bob@example.com/laptop'
    id='disco1'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
  

<iq type='result'
    from='bob@example.com/laptop'
    to='alice@example.org/pda'
    id='disco1'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <identity category='client' type='pc'/>
    ...
    <feature var='http://jabber.org/protocol/esession'/>
    ...
  </query>
</iq>
  

4.1 ESession Request

In addition to the "accept", "logging" and "secure" fields specified in Chat Session Negotiation, Alice MUST send to Bob each of the ESession options (see list below) that she is willing to use, in her order of preference (see Mandatory to Implement Technologies). Note: Alice SHOULD NOT include a "reason" field since Aunt Tillie may not be aware the ESession request is not encrypted.

1. The list of Modular Exponential (MODP) group numbers (as specified in RFC 2409 [9] or RFC 3526 [10]) that MAY be used for Diffie-Hellman key exchange (valid group numbers include 1,2,3,4,5,14,15,16,17 and 18)

2. Symmetric block cipher algorithm names

3. Hash algorithm names

4. Signature algorithm names

5. Compression algorithm names

6. The list of stanza types that MAY be encrypted and decrypted

7. Whether or not the other entity MUST send the fingerprint (PKID) of its public signature-verification key instead of the full key [11]

8. The different versions of this protocol that are supported [12]

9. The minimum number of stanzas that MUST be exchanged before an entity MAY initiate a key re-exchange (1 - every stanza, 100 - every hundred stanzas). Note: This value MUST be less than 232 (see Re-Keying Limits)

Each MODP group has at least two well known constants: a large prime number p, and a generator g for a subgroup of GF(p). For each MODP group that Alice specifies she MUST perform the following computations to calculate her Diffie-Hellman keys (where n is the number of bits per cipher block for the block cipher algorithm with the largest block size out of those she specified):

1. Generate a secret random number x (where 22n-1 < x < p - 1)

2. Calculate e = gx mod p

Alice MUST send all her calculated values of e to Bob (in the same order as the associated MODP groups are being sent). She MUST also specify randomly generated Base64 encoded (in accordance with Section 3 of RFC 3548 [13]) value of NA (her ESession ID).

Example 3. Alice Requests an ESession

<message from='alice@example.org/pda' to='bob@example.com'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    <x type='form' xmlns='jabber:x:data'>
      <field type="hidden" var="FORM_TYPE">
        <value>http://jabber.org/protocol/chatneg</value>
      </field>
      <field type="boolean" var="accept">
        <value>1</value>
      </field>
      <field type="boolean" var="logging">
        <value>1</value>
      </field>
      <field type="boolean" var="secure">
        <value>0</value>
      </field>
      <field type="list-single" var="modp">
        <option><value>5</value></option>
        <option><value>14</value></option>
        <option><value>2</value></option>
      </field>
      <field type="list-single" var="crypt_algs">
        <option><value>aes256-ctr</value></option>
        <option><value>twofish256-ctr</value></option>
        <option><value>aes128-ctr</value></option>
      </field>
      <field type="list-single" var="hash_algs">
        <option><value>whirlpool</value></option>
        <option><value>sha256</value></option>
      </field>
      <field type="list-single" var="sign_algs">
        <option><value>rsa</value></option>
        <option><value>dsa</value></option>
      </field>
      <field type="list-single" var="compress">
        <option><value>none</value></option>
      </field>
      <field type="list-multi" var="stanzas">
        <option><value>message</value></option>
        <option><value>iq</value></option>
        <option><value>presence</value></option>
      </field>
      <field type="boolean" var="pk_hash">
        <value>0</value>
      </field>
      <field type="list-single" var="ver">
        <option><value>1.3</value></option>
        <option><value>1.2</value></option>
      </field>
      <field type="text-single" var="rekey_freq">
        <value>1</value>
      </field>
      <field var="my_nonce">
        <value> ** Base64 encoded ESession ID ** </value>
      </field>
      <field var="keys">
        <value> ** Base64 encoded value of e5 ** </value>
        <value> ** Base64 encoded value of e14 ** </value>
        <value> ** Base64 encoded value of e2 ** </value>
      </field>
    </x>
  </feature>
  <amp xmlns='http://jabber.org/protocol/amp' per-hop='true'>
    <rule action='drop' condition='deliver' value='stored'/>
  </amp>
</message>
      

If Bob does not support one or more of the options in each ESession field, then he SHOULD return a <feature-not-implemented/> error (but he MAY return no error if, for example, he does not want to reveal his presence to Alice for whatever reason):

Example 4. Bob Informs Alice that Her Options Are Not Supported

<message type='error'
         from='bob@example.com/laptop'
         to='alice@example.org/pda'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    ...
  </feature>
  <error type='cancel'>
    <feature-not-implemented xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/>
    <unsupported-options xmlns='http://jabber.org/protocol/esession#error'/>
  </error>
</message>
      

Either Bob or Alice MAY attempt to initiate a new ESession after any error during the negotiation process. However, both MUST consider the previous negotiation to have failed and MUST discard any information learned through the previous negotiation.

If Bob is unwilling to start an ESession, but he is ready to initiate a one-to-one chat session with Alice (see Chat Session Negotiation), then he SHOULD accept the Chat Session and terminate the ESession negotiation by not including a 'nonce' field in his response.

Example 5. Bob Accepts Chat Session

<message from='bob@example.com/laptop' to='alice@example.org/pda'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    <x type='submit' xmlns='jabber:x:data'>
      <field var="FORM_TYPE">
        <value>http://jabber.org/protocol/chatneg</value>
      </field>
      <field var="accept"><value>1</value></field>
      <field var="logging"><value>0</value></field>
      <field var="secure"><value>0</value></field>
    </x>
  </feature>
</message>
      

4.2 Diffie-Hellman Preparation (Bob)

If Bob supports one or more of each of Alice's ESession options and is willing to start an ESession with Alice, then he MUST select one of the options from each of the ESession fields he received from Alice including one hash algorithm ("HASH"), and one of the MODP groups and Alice's corresponding value of e (see RFC 3766 [14] or RFC 3526 for recommendations regarding balancing the sizes of symmetric cipher blocks and Diffie-Hellman moduli).

Each MODP group has at least two well known constants: a large prime number p, and a generator g for a subgroup of GF(p). Bob SHOULD return a <feature-not-implemented/> error unless: 1 < e < p - 1

Bob MUST then perform the following computations (where n is the number of bits per cipher block for the selected block cipher algorithm):

1. Generate a random number NB (his ESession ID)

2. Generate an n-bit random number CA (the block cipher counter for stanzas sent from Alice to Bob)

3. Set CB = CA XOR 2n-1 (where CB is the block counter for stanzas sent from Bob to Alice)

4. Generate a secret random number y (where 22n-1 < y < p - 1)

5. Calculate d = gy mod p

6. Calculate K = HASH(ey mod p) (the shared secret)

4.3 Generating Session Keys

Bob MUST use the shared secret ("K") and the selected hash algorithm ("HASH") to generate two sets of three keys, one set for each direction of the ESession.

For stanzas that Alice will send to Bob, the keys are calculated as:

1. Encryption key KCA = HASH(K, 0)

2. Integrity key KMA = HASH(K, 2)

3. SIGMA key KSA = HASH(K, 4)

For stanzas that Bob will send to Alice the keys are calculated as:

4. Encryption key KCB = HASH(K, 1)

5. Integrity key KMB = HASH(K, 3)

6. SIGMA key KSB = HASH(K, 5)

Once the sets of keys have been calculated the value of K MUST be securely destroyed.

Note: As many bits of key data as are needed for each key MUST be taken from the least significant bits of the hash output. When negotiating a hash, entities MUST ensure that the hash output is no shorter than the required key data. For algorithms with variable-length keys the maximum length (up to the hash output length) SHOULD be used.

4.4 Hiding Identity

Bob MUST perform the following steps before he can prove his identity to Alice while protecting it from third parties.

1. Select pubKeyB, the public key Alice should use to authenticate his signature with the signature algorithm he selected ("SIGN").

2. Set formB to the Normalized content of the reponse data form he will send back to Alice (including his responses for all the fields he received from Alice).

   Bob MUST encapsulate the Base64 encoded values of CA and Alice's NA in two new 'counter' and 'nonce' fields and add them to formB. Note: The 'pk_hash' field specifies whether or not Alice MUST send the fingerprint (PKID) of her public signature-verification key instead of her full key. Note: The value of the 'rekey_freq' field MUST be less than 232 and greater than or equal to the value specified by Alice. Note: Bob MUST place his Base64 encoded values of NB and d in the 'my_nonce' and 'keys' fields. Bob MUST NOT return Alice's values of e.

3. Concatenate Alice's ESession ID, Bob's ESession ID, d, pubKeyB and formB, and calculate the HMAC (as defined in Section 2 of RFC 2104 [15]) of the resulting byte string using the selected hash algorithm ("HASH") and the key KSB.

   macB = HMAC(HASH, KSB, {NA, NB, d, pubKeyB, formB})

4. Calculate signB, the signature of the HMAC result using his private signature key that corresponds to pubKeyB

   signB = SIGN(signKeyB, macB)

5. If the value of the 'pk_hash' field that Alice sent Bob was true then Bob SHOULD set pubKeyB to the key's fingerprint

   if (pk_hash) pubKeyB = HASH(pubKeyB)

6. Concatenate pubKeyB and signB and encrypt the resulting byte string with the agreed algorithm ("CIPHER") in counter mode (see Recommendation for Block Cipher Modes of Operation [16]), using the encryption key KCB and block counter CB. Note: CB MUST be incremented by 1 for each encrypted block or partial block (i.e. CB = (CB + 1) mod 2n, where n is the number of bits per cipher block for the agreed block cipher algorithm).

   IDB = CIPHER(KCB, CB, {pubKeyB, signB})

7. Calculate the HMAC of the encrypted identity (IDB) and the value of Bob's block cipher counter CB before the encryption above using the selected hash algorithm ("HASH") and the integrity key KMB.

   MB = HMAC(HASH, KMB, CB, IDB)

4.5 ESession Response

Bob responds to Alice by sending her formB.

Example 6. Bob Responds to Alice (4-Message Negotiation)

<message from='bob@example.com/laptop' to='alice@example.org/pda'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    <x type='submit' xmlns='jabber:x:data'>
      <field var="FORM_TYPE">
        <value>http://jabber.org/protocol/chatneg</value>
      </field>
      <field var="accept"><value>1</value></field>
      <field var="logging"><value>0</value></field>
      <field var="secure"><value>0</value></field>
      <field var="modp"><value>5</value></field>
      <field var="crypt_algs"><value>aes256-ctr</value></field>
      <field var="hash_algs"><value>sha256</value></field>
      <field var="sign_algs"><value>rsa</value></field>
      <field var="compress"><value>none</value></field>
      <field var="stanzas"><value>message</value></field>
      <field var="pk_hash"><value>1</value></field>
      <field var="ver"><value>1.3</value></field>
      <field var="rekey_freq"><value>50</value></field>
      <field var="my_nonce">
        <value> ** Base64 encoded ESession ID ** </value>
      </field>
      <field var="keys">
        <value> ** Base64 encoded value of d ** </value>
      </field>
      <field var="nonce">
        <value> ** Base64 encoded ESession ID ** </value>
      </field>
      <field var="counter">
        <value> ** Base64 encoded block counter ** </value>
      </field>
    </x>
  </feature>
</message>
    

If Bob prefers the RECOMMENDED 3-message ESession negotiation, where Alice's identity is protected from active attacks instead of his own, then he should encapsulate the Base64 encoded values of IDB and MB in data form fields ('identity' and 'mac'), and append the new fields to formB before sending it to Alice.

Example 7. Bob Responds to Alice (3-Message Negotiation)

<message from='bob@example.com/laptop' to='alice@example.org/pda'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    <x type='submit' xmlns='jabber:x:data'>
      <field var="FORM_TYPE">
        <value>http://jabber.org/protocol/chatneg</value>
      </field>
      <field var="accept"><value>1</value></field>
      <field var="logging"><value>0</value></field>
      <field var="secure"><value>0</value></field>
      <field var="modp"><value>5</value></field>
      <field var="crypt_algs"><value>aes256-ctr</value></field>
      <field var="hash_algs"><value>sha256</value></field>
      <field var="sign_algs"><value>rsa</value></field>
      <field var="compress"><value>none</value></field>
      <field var="stanzas"><value>message</value></field>
      <field var="pk_hash"><value>1</value></field>
      <field var="ver"><value>1.3</value></field>
      <field var="rekey_freq"><value>50</value></field>
      <field var="my_nonce">
        <value> ** Base64 encoded ESession ID ** </value>
      </field>
      <field var="keys">
        <value> ** Base64 encoded value of d ** </value>
      </field>
      <field var="nonce">
        <value> ** Base64 encoded ESession ID ** </value>
      </field>
      <field var="counter">
        <value> ** Base64 encoded block counter ** </value>
      </field>
      <field var="identity">
        <value> ** Encrypted identity ** </value>
      </field>
      <field var="mac">
        <value> ** Integrity of identity ** </value>
      </field>
    </x>
  </feature>
</message>
    

4.6 Diffie-Hellman Preparation (Alice)

After Alice receives Bob's response, she MUST use the value of d and the ESession options specified in Bob's response to perform the following steps (where p and g are the constants associated with the selected MODP group, HASH is the selected hash algorithm, and n is the number of bits per cipher block for the agreed block cipher algorithm):

1. Return a <feature-not-implemented/> error to Bob if she is not prepared to support any of the ESession options specified by Bob (if any of the options were not included in her initial ESession request)

2. Return a <feature-not-implemented/> error to Bob unless: 1 < d < p - 1

3. Set CB = CA XOR 2n-1 (where CB is the block counter for stanzas sent from Bob to Alice)

4. Select her values of x and e that correspond to the selected MODP group (from all the values of x and e she calculated previously)

5. Calculate K = HASH(dx mod p) (the shared secret)

6. Generate the session keys (KCA, KMA, KSA, KCB, KMB and KSB) in the same way as Bob did (see Generating Session Keys)

4.7 Verifying Bob's Identity

If Bob included 'identity' and 'mac' fields in his response then Alice MUST also perform the following steps:

1. Calculate the HMAC of the encrypted identity (IDB) and the value of Bob's block cipher counter using HASH and the integrity key KMB.

   MB = HMAC(HASH, KMB, CB, IDB)

2. Return a <feature-not-implemented/> error to Bob unless the value of MB she calculated matches the one she received in the 'mac' field

3. Obtain pubKeyB and signB by decrypting IDB with the agreed symmetric block cipher algorithm ("DECIPHER") in counter mode, using the encryption key KCB and block counter CB. Note: CB MUST be incremented by 1 for each encrypted block or partial block (i.e. CB = (CB + 1) mod 2n, where n is the number of bits per cipher block for the agreed block cipher algorithm).

   {pubKeyB, signB} = DECIPHER(KCB, CB, IDB)

4. If the value of the 'pk_hash' field she sent to Bob in her ESession Request was true, then Alice SHOULD change the value of pubKeyB to be her copy of the public key whose HASH matches the value of pubKeyB that she received from Bob. Note: If she cannot find a copy of the public key then Alice MUST terminate the ESession. She MAY then request a new ESession with the 'pk_hash' field set to false.

5. Return a <feature-not-implemented/> error to Bob unless she can confirm (or has previously confirmed) that pubKeyB really is Bob's public key, for examples, via secure out-of-band communication, or through a third-party authority (see Verifying Keys).

6. Set the value of formB to be the Normalized content of the form she received from Bob without any 'identity' or 'mac' fields.

7. Concatenate Alice's ESession ID, Bob's ESession ID, d, pubKeyB and formB, and calculate the HMAC of the resulting byte string using HASH and the key KSB.

   macB = HMAC(HASH, KSB, {NA, NB, d, pubKeyB, formB})

8. Return a <feature-not-implemented/> error to Bob unless she can use pubKeyB with the selected signature verification algorithm ("VERIFY") to confirm that signB is the signature of the HMAC result (see Signature Verification).

   VERIFY(signB, pubKeyB, macB)

4.8 ESession Completion

Alice MUST then prove her identity to Bob while protecting it from third parties. She MUST perform the steps equivalent to those Bob performed above (see Hiding Identity for a more detailed description). Alice's calculations are summarised below (pay attention to the order of NB and NA when calculating macA). Note: formA is the Normalized content of the ESession Request data form that she sent to Bob previously.

macA = HMAC(HASH, KSA, {NB, NA, e, pubKeyA, formA})

signA = SIGN(signKeyA, macA)

if (pk_hash) pubKeyA = HASH(pubKeyA)

IDA = CIPHER(KCA, CA, {pubKeyA, signA})

MA = HMAC(HASH, KMA, CA, IDA)

Alice MUST send the Base64 encoded values of NB, IDA and MA to Bob. If Alice has already confirmed Bob's identity (i.e. if Bob included 'identity' and 'mac' fields in his response), then she MAY also send encrypted content (see Exchanging Stanzas) in the same stanza as the proof of her identity.

Example 8. Alice Sends Bob Her Identity

<message from='alice@example.org/pda' to='bob@example.com/laptop'>
  <feature xmlns='http://jabber.org/protocol/feature-neg'>
    <x type='result' xmlns='jabber:x:data'>
      <field var="FORM_TYPE"><value>http://jabber.org/protocol/chatneg</value></field>
      <field var="nonce"><value> ** Base64 encoded ESession ID ** </value></field>
      <field var="identity"><value> ** Encrypted identity ** </value></field>
      <field var="mac"><value> ** Integrity of identity ** </value></field>
    </x>
  </feature>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <data> ** Base64 encoded m_final ** </data>
    <mac> ** Base64 encoded a_mac ** </mac>
  </encrypted>
</message>
      

If Alice also includes a <terminate/> element (see ESession Termination) within the <encrypted/> element then the ESession is terminated immediately. Note: This special case, where a single stanza is encrypted and sent in isolation, is equivalent to object encryption (or object signing if no encryption is specified) and offers several significant advantages over non-session approaches - including perfect forward secrecy.

After receiving Alice's identity Bob MUST verify it by performing steps equivalent to those described in the section Verifying Bob's Identity above. Some of Bob's calculations are summarised below (pay attention to the order of NB and NA when calculating macA). Note: formA is the Normalized content of the ESession Request data form (the first form) that Alice sent him. Note: If Bob sends an error to Alice then he SHOULD ignore any encrypted content he received in the stanza.

MA = HMAC(HASH, KMA, CA, IDA)

{pubKeyA, signA} = DECIPHER(KCA, CA, IDA)

macA = HMAC(HASH, KSA, {NB, NA, e, pubKeyA, formA})

VERIFY(signA, pubKeyA, macA)

If Alice has already confirmed Bob's identity (i.e. if Bob included 'identity' and 'mac' fields in his response above), then the ESession negotiation is complete.

Otherwise, one more step is necessary. Bob MUST send Alice the Base64 encoded values of NA, IDB and MB that he calculated previously (see Hiding Identity). Note: He MAY also send encrypted content (see Exchanging Stanzas) in the same stanza.

Example 9. Bob Sends Alice His Identity

<message from='bob@example.com/laptop' to='alice@example.org/pda'>
  <init xmlns='http://jabber.org/protocol/esession#init'>
    <x type='result' xmlns='jabber:x:data'>
      <field var="FORM_TYPE"><value>http://jabber.org/protocol/chatneg</value></field>
      <field var="nonce"><value> ** Base64 encoded ESession ID ** </value></field>
      <field var="identity"><value> ** Encrypted identity ** </value></field>
      <field var="mac"><value> ** Integrity of identity ** </value></field>
    </x>
  </init>
</message>
      

After receiving Bob's identity Alice MUST verify it by performing steps described in the section Verifying Bob's Identity above. Note: If Alice sends an error to Bob then she SHOULD ignore any encrypted content she received in the stanza.

5.1 Encryptable Content

Once ESession negotiation is complete, Alice and Bob MUST exchange only encrypted forms of the one-to-one stanza types they agreed upon (e.g., <message/> and <iq/> stanzas).

Either Alice or Bob MAY send encrypted stanzas. Here we describe the process where Alice sends Bob an encrypted stanza. She MUST only encrypt the XML content that would normally be ignored by the intermediate servers. She MUST NOT encrypt stanza wrapper elements or Advanced Message Processing elements.

Example 10. Unencrypted Stanza

<message from='alice@example.org/pda'
         to='bob@example.com/laptop'
         type='chat'>
  <body>Hello, Bob!</body>
  <amp xmlns='http://jabber.org/protocol/amp'>
    <rule action='error' condition='match-resource' value='exact'/>
  </amp>
  <active xmlns='http://jabber.org/protocol/chatstates'/>
</message>

Example 11. XML Content to be Encrypted

<body>Hello, Bob!</body>
<active xmlns='http://jabber.org/protocol/chatstates'/>

5.2 Encryption

Alice MUST perform the following steps to encrypt the XML content. Note: if there is no XML content to be encrypted (e.g. if this is an empty Re-Keying or Termination stanza), then CA MUST be incremented by 1 (see below), and only the last two steps (normalization and MAC calculation) should be performed.

1. Serialize the XML content she wishes to send into an array of UTF-8 bytes, m. [17]

2. Compress m using the negotiated algorithm. If a compression algorithm other than 'none' was agreed, the compression context is typically initialized after key exchange and passed from one stanza to the next, with only a partial flush at the end of each stanza. [18]

   m_compressed = compress(m)

3. Encrypt the data with the agreed algorithm in counter mode, using the encryption key KCA. Note: CA MUST be incremented by 1 for each encrypted block or partial block (i.e. CA = (CA + 1) mod 2n, where n is the number of bits per cipher block for the agreed block cipher algorithm). Note: if the block cipher algorithm 'none' was agreed (see Unencrypted ESessions) then encryption MUST NOT be performed and CA MUST be incremented by 1 (for replay protection).

   m_final = encrypt(KCA, CA, m_compressed)

4. Alice MUST now create the Normalized XML content of the <encrypted/> XML element. If there is encrypted XML content, the XML MUST include the Base64 encoded value of m_final wrapped in a <data/> element. Note: the <encrypted/> element MAY also contain one <terminate/> element (see Termination), one <key/> element and one or more <old/> elements (see Re-Keying).

   m_content = '<data> ** Base64 encoded m_final ** </data>'

5. The XML content and the value of Alice's block cipher counter CA before the data was encrypted, are now processed through the HMAC algorithm, along with the agreed hash algorithm ("HASH") and the integrity key KMA.

   a_mac = HMAC(HASH, KMA, m_content, CA)

5.3 Sending an Encrypted Stanza

Before sending the stanza to Bob, Alice MUST wrap m_content and the Base64 encoded value of a_mac (wrapped in a <mac/> element) inside an <encrypted/> element and insert it into the stanza in place of the original content. There MUST NOT be more than one <encrypted/> element per stanza.

Example 12. Message Stanza with Encrypted Content

<message from='alice@example.org/pda'
         to='bob@example.com/laptop'
         type='chat'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <data> ** Base64 encoded m_final ** </data>
    <mac> ** Base64 encoded a_mac ** </mac>
  </encrypted>
  <amp xmlns='http://jabber.org/protocol/amp' per-hop='true'>
    <rule action='error' condition='match-resource' value='exact'/>
  </amp>
</message>
    

5.4 Decryption

When Bob receives the stanza from Alice, he extracts and Base64 decodes the values of m_final and a_mac from the content and performs the following steps.

1. Remove the <mac/> element from the <encrypted/> element and Normalize the remaining XML content. Calculate the Message Authentication Code (MAC) for the content.

   b_mac = HMAC(HASH, KMA, m_content, CA)

2. Verify that b_mac and a_mac match. If they are not identical, the content has been tampered with and Bob MUST terminate the ESession, he MAY send a <not-acceptable/> error to Alice. [19]

3. Decrypt m_final using the agreed algorithm, KCA and CA. Note: CA MUST be incremented by 1 for each decrypted block (see Encryption). Note: if the block cipher algorithm 'none' was agreed decryption MUST NOT be performed and CA MUST be incremented by 1.

   m_compressed = decrypt(KCA, CA, m_final)

4. Decompress m_compressed using the negotiated algorithm (usually 'none').

   m = decompress(m_compressed)

5. Replace the <encrypted/> element in the serialized XML stanza with m and feed the stanza into an XML parser. If the parser returns an XML format error then Bob MUST terminate the ESession, he MAY send a <not-acceptable/> error to Alice. [20]

6.1 Re-Key Initiation

Either Alice or Bob MAY initiate a key re-exchange. Here we describe the process initiated by Alice. First she MUST calculate new values for the encryption parameters:

1. Generate a secret random number x (where 22n-1 < x < p - 1, where n is the number of bits per cipher block for the agreed block cipher algorithm)

2. Calculate e = gx mod p

3. Calculate K = dx mod p (the new shared secret)

4. Calculate KCA, KMA, KCB, KMB from K (see Generating Session Keys)

To avoid extra stanzas, the new value of e SHOULD be sent to Bob along with an encrypted stanza. Note: Alice MUST NOT use the new KCA and KMA to encrypt this stanza or to calculate the MAC. However, she MUST use them when sending subsequent stanzas.

Note: There is no need for Alice to provide a signature because the calculation of the MAC includes the new value of e, see Exchanging Stanzas).

Example 13. Alice Sends Re-Key Stanza

<message from='alice@example.org/pda' to='bob@example.com/laptop'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <data> ** Base64 encoded m_final ** </data>
    <key> ** Base64 encoded value of new e ** </key>
    <mac> ** Base64 encoded a_mac ** </mac>
  </encrypted>
</message>
    

Note: Bob may not receive the new key before he sends his next stanzas (they may cross in transit). So, before destroying her old values of KCB and KMB, Alice MUST wait until either she receives a stanza encrypted with the new key, or a reasonable time has passed (60 seconds should cover a network round-trip and calculations by a constrained client). Similarly she MUST wait before destroying her old value of x, in case Bob sends two stanzas before receiving Alice's new key (the first stanza might include a re-key).

6.2 Re-Key Acceptance

After Bob has received a stanza with a new value of e, has confirmed it is greater than one, and has decrypted the stanza with the old value of KCA, he MUST securely destroy all copies of KCA and KCB and perform the following calculations with the new value of e:

1. Calculate K = ey mod p

2. Calculate KCA, KMA, KCB, KMB from K (see Generating Session Keys)

He MUST use these new values to encrypt and decrypt all subsequent stanzas. [21]

The next time Bob sends Alice a stanza he MUST specify the number of rekeys he has received from her since he sent her his last stanza. He does that by setting the 'rekeys' attribute of the <data/> element. Note: The default value of the 'rekeys' attribute is zero.

Example 14. Bob's First Stanza After Receiving a Re-Key

<message from='bob@example.com/laptop' to='alice@example.org/pda'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <data rekeys='1'> ** Base64 encoded m_final ** </data>
    <mac> ** Base64 encoded b_mac ** </mac>
  </encrypted>
</message>
    

When Alice receives the stanza from Bob she MUST use the 'rekeys' attribute to decide which of her values of KCB and KMB (or x) she should use to decrypt the stanza - otherwise she would not know if Bob received her rekey(s) before he sent the stanza. Once she is sure Bob has received her rekey(s) she MUST discard all her older values of KCB, KMB and x.

6.3 Publishing Old MAC Values

Once the expired MAC keys have been published, anyone could create valid arbitrary stanzas with them. This prevents anyone being able to prove the authenticity of a transcript of the ESession in the future.

Either entity MAY publish old values of KMA and/or KMB within any encrypted stanza as long as it knows that all the stanzas that MAY use the old values have been received and validated. Note: A 'man-in-the-middle' could delay the delivery of stanzas indefinitely. So, before Alice publishes KMA (and KMB), she MUST wait until she has both sent a re-key to Bob and received a stanza from Bob encrypted with her new key. (She MAY also publish KMB after she has received a re-key from Bob.)

Example 15. Publishing Expired MAC Keys

<message from='alice@example.org/pda' to='bob@example.com/laptop'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <data> ** Base64 encoded m_final ** </data>
    <old> ** Base64 encoded old MAC key ** </old>
    <old> ** Base64 encoded old MAC key ** </old>
    <mac> ** Base64 encoded a_mac ** </mac>
  </encrypted>
</message>
    

Entities SHOULD ignore any <old/> elements they receive.

<message from='alice@example.org/pda' to='bob@example.com/laptop'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <terminate>1</terminate>
    <old> ** Base64 encoded old MAC key ** </old>
    <mac> ** Base64 encoded a_mac ** </mac>
  </encrypted>
</message>
    

<message from='alice@example.org/pda' to='bob@example.com/laptop'>
  <encrypted xmlns='http://jabber.org/protocol/esession'>
    <terminate>1</terminate>
    <old> ** Base64 encoded old MAC key ** </old>
    <mac> ** Base64 encoded b_mac ** </mac>
  </encrypted>
</message>
    

8.1 XML Normalization

Before the signature or MAC of a block of XML is generated or verified, all character data between all elements MUST be removed and the XML MUST be converted to canonical form (see Canonical XML [23]).

All the XML this protocol requires to be signed or MACed is very simple, so in this case, canonicalization SHOULD only require the following changes:

• Set attribute value delimiters to quotation marks (i.e. simply replace all single quotes in the serialized XML with double quotes)
• Impose lexicographic order on the attributes of "field" elements (i.e. ensure "type" is before "var")

Implementations MAY conceivably also need to make the following changes. Note: Empty elements and special characters SHOULD NOT appear in the signed or MACed XML specified in this protocol.

• Ensure there are no character references
• Convert empty elements to start-end tag pairs
• Ensure there is no whitespace except for single spaces before attributes

8.2 Hash

Before the signature or MAC of a block of XML is generated or verified, the agreed hash algorithm MUST be used to generate the hash of the normalized XML.

m_hash = HASH(m_content)

8.3 Generation

The signature generation depends on the type of private key being used.

signature_rsa = rsa_sign(rsa_private_key, m_hash, hashOID)

sig_dsa_r, sig_dsa_s = dsa_sign(dsa_private_key, m_hash)

8.4 Signature Format

The signature formats are the same for all public key formats. All integers are stored in big-endian byte order.

8.5 Verification

The signature verification depends on the type of public key being used.

boolean = rsa_verify(signature_rsa, m_hash, hashOID, rsa_modulus, rsa_public_exponent)

boolean = dsa_verify(sig_dsa_r, sig_dsa_s, m_hash, dsa_p, dsa_q, dsa_g, dsa_y)

9.1 Random Numbers

Weak pseudo-random number generators (PRNG) enable successful attacks. Implementors MUST use a cryptographically strong PRNG to generate all random numbers (see RFC 1750 [26]).

9.2 Re-Keying Limits

After a key exchange an entity MUST NOT exchange a total of 232 encrypted blocks before it initiates a key re-exchange (see RFC 4344 [27]). Note: This limitation also ensures the same key and counter values are never used to encrypt two different blocks using counter mode (thus preventing simple attacks).

In order to reduce the Perfect Forward Secrecy window of vulnerability, after an extended period of activity, entities SHOULD either re-key or terminate the ESession.

9.3 Verifying Keys

The trust system outlined in this document is based on Alice trusting that the public key presented by Bob is actually Bob's key (and vice versa). Determining this trust may be done in a variety of ways depending on the entities' support for different public key (certificate) formats, signing algorithms and signing authorities. For instance, if Bob publishes a PGP/GPG public key, Alice MAY verify that his key is signed by another key that she knows to be good. Or, if Bob provides an X.509 certificate, she MAY check that his key has been signed by a Certificate Authority that she trusts.

When trust cannot be achieved automatically, methods that are not transparent to the users may be employed. For example, Bob could communicate the SHA-256 fingerprint of his public key to Alice via secure out-of-band communication (e.g. face-to-face). This would enable Alice to confirm that the public key she receives in-band is valid. Note however that very few people bother to verify fingerprints in this way. So this method is exceptionally vulnerable to 'man-in-the-middle' attacks. In order to reduce the window of vulnerability, an entity SHOULD remember the fingerprints of all user-validated public keys and alert the user in the future if ever the fingerprint(s) it stored for an entity do not match any of the received public keys.

Alternatively Alice and Bob could agree a shared secret via secure out-of-band communication, Bob could then use it to create an HMAC of his public key that only Alice could verify.

Note: If no keys are acceptable to Alice (because Alice has never verified any of the keys, and because either the keys are not signed, or Alice does not support the signature algorithms of the keys, or she cannot parse the certificate formats, or she does not recognise the authorities that signed the keys) then, although the ESession can still be encrypted, she cannot be sure she is communicating with Bob.

9.4 Replay Attacks

The block cipher counters maintained implicitly by Alice and Bob (CA and CB) prevent stanzas being replayed within any ESession. They ensure that the MAC will be different for all stanzas, even if the HMAC key and the content of the stanza are identical.

Alice and Bob MUST ensure that the value of e or d they provide when negotiating each online ESession is unique. This prevents complete online ESessions being replayed.

9.5 Unencrypted ESessions

Organisations with full disclosure policies may require entities to disable encryption to enable the logging of all messages on their server. Unencrypted ESessions meet all the Security Requirements except for Confidentiality. Unencrypted ESessions enable Alice to to confirm securely with Bob that both client-server connections are secure. i.e. that the value of the 'secure' option (as specified in Chat Session Negotiation) has not been tampered with.

9.6 Storage

If either entity stores a (re-encrypted) transcript of an ESession for future consultation then the Perfect Forward Secrecy offered by this protocol is lost. If the negotiated value of the 'logging' Chat Session Negotiation field is false the entities SHOULD NOT store any part of the ESession content (not even in encrypted form).

9.7 Extra Responsabilities of Implementors

Cryptography plays only a small part in an entity's security. Even if it implements this protocol perfectly it may still be vulnerable to other attacks. For examples, an implementation might store ESession keys on swap space or save private keys to a file in cleartext! Implementors MUST take very great care when developing applications with secure technologies.

9.8 Mandatory to Implement Technologies

An implementation of ESession MUST support the Diffie-Hellman Key Agreement and HMAC algorithms. Note: The parameter names mentioned below are related to secure shell; see SSH Transport Layer Encryption Modes for block cipher algorithm details; see the IANA Secure Shell Protocol Parameters Registry [28] for other names.

11.1 Namespaces

Upon approval of this JEP, the Jabber Registrar [38] shall register the following namespaces:

• http://jabber.org/protocol/esession
• http://jabber.org/protocol/esession#init
• http://jabber.org/protocol/esession#error

11.2 Field Standardization

Field Standardization for Data Forms [39] defines a process for standardizing the fields used within Data Forms qualified by a particular namespace. The following fields shall be registered for use in both Encrypted Sessions and Chat Session Negotiation:

Registry Submission

<form_type>
  <name>http://jabber.org/protocol/esession</name>
  <jep>JEP-0116</jep>
  <desc>ESession negotiation forms</desc>
  <field
      var='match_resource'
      type='text-single'
      label='Target resource for offline ESessions'/>
  <field
      var='modp'
      type='list-single'
      label='MODP group number'/>
  <field
      var='crypt_algs'
      type='list-single'
      label='Symmetric block cipher options'/>
  <field
      var='hash_algs'
      type='list-single'
      label='Hash algorithm options'/>
  <field
      var='sign_algs'
      type='list-single'
      label='Signature algorithm options'/>
  <field
      var='compress'
      type='list-single'
      label='Compression algorithm options'/>
  <field
      var='stanzas'
      type='list-multi'
      label='Stanzas types to encrypt'/>
  <field
      var='pk_hash'
      type='boolean'
      label='Respond with public key fingerprint'/>
  <field
      var='ver'
      type='list-single'
      label='Supported versions of JEP-0116'/>
  <field
      var='rekey_freq'
      type='text-single'
      label='Minimum number of stanzas between key exchanges'/>
  <field
      var='keys'
      type='hidden'
      label='Diffie-Hellman keys'/>
  <field
      var='my_nonce'
      type='hidden'
      label='ESession ID of Sender'/>
  <field
      var='expires'
      type='hidden'
      label='Expiry time of offline ESession options'/>
  <field
      var='nonce'
      type='hidden'
      label='ESession ID of Receiver'/>
  <field
      var='counter'
      type='hidden'
      label='Initial block counter'/>
  <field
      var='pkids'
      type='list-single'
      label='Public key IDs'/>
  <field
      var='signs'
      type='list-single'
      label='Data form signatures'/>
</form_type>

<form_type>
  <name>http://jabber.org/protocol/chatneg</name>
  <jep>JEP-0155</jep>
  ...
</form_type>
    

13.1 To Think About

1. Standardise on the X.509 public key and signature formats?
2. What challenges exist to make the OTR Gaim Plugin use this protocol natively when talking to Jabber entities? Can these be mitigated by 'non-critical' protocol changes?
3. Would anything in this protocol (e.g., its dependency on in-order stanza delivery) prevent an XMPP entity using it to exchange encrypted messages and presence with a user of a non-XMPP messaging system, assuming that the gateway both supports this protocol and is compatible with a purpose-built security plugin on the other user's client (e.g. a Gaim plugin connects to the gateway via a non-XMPP network)?
4. Could use Flexible Offline Message Retrieval [40] (FOMR) instead of AMP to prevent any offline ESessions Bob can't decrypt being delivered to him. (Each <item/> that corresponds to an ESession message would have to contain a <ESessionID/> child, to allow Bob to discover which of his stored values of y was used to encrypt the message.)

13.2 To Do

1. Ask the authors of AMP to explain how to achieve the match_resource functionality to be specified in JEP-0187.
2. Define names for X.509 SubjectPublicKeyInfo public key formats (different to X.509 certificates). This format must be used when keys are distributed within session negotiation.
3. Add non-repudiable signing option
4. Perhaps the JEP needs to specify more carefully how block counters are handled between messages, especially in the event of partial blocks?
5. Give examples of specific errors and discuss error scenarios throughout document (e.g., what should Bob do if he is not offline and he receives an offline key exchange stanza?).
6. Update Dependencies list
7. Define an optional protocol that would allow Alice to store values of NA and x (and the PKIDs she trusts) 'securely' on her own server (before she goes offline).

1. JEP-0027: Current Jabber OpenPGP Usage <http://www.jabber.org/jeps/jep-0027.html>.

2. RFC 3862: Common Presence and Instant Messaging (CPIM): Message Format <http://www.ietf.org/rfc/rfc3862.txt>.

3. RFC 3863: Presence Information Data Format (PIDF) <http://www.ietf.org/rfc/rfc3863.txt>.

4. RFC 3923: End-to-End Signing and Object Encryption for the Extensible Messaging and Presence Protocol (XMPP) <http://www.ietf.org/rfc/rfc3923.txt>.

5. JEP-0188: Cryptographic Design of Encrypted Sessions <http://www.jabber.org/jeps/jep-0188.html>.

6. JEP-0030: Service Discovery <http://www.jabber.org/jeps/jep-0030.html>.

7. JEP-0115: Entity Capabilities <http://www.jabber.org/jeps/jep-0115.html>.

8. JEP-0155: Chat Session Negotiation <http://www.jabber.org/jeps/jep-0155.html>.

9. RFC 2409: The Internet Key Exchange (IKE) <http://www.ietf.org/rfc/rfc2409.txt>.

10. RFC 3526: More Modular Exponential (MODP) Diffie-Hellman Groups <http://www.ietf.org/rfc/rfc3526.txt>.

11. If the entity already possesses one of the other entity's public keys then it is RECOMMENDED that only the fingerprint is requested from the other entity - since this saves bandwidth.

12. This version of this document describes version 1.0 of this protocol.

13. RFC 3548: The Base16, Base32, and Base64 Data Encodings <http://www.ietf.org/rfc/rfc3548.txt>.

14. RFC 3766: Determining Strengths For Public Keys Used For Exchanging Symmetric Keys <http://www.ietf.org/rfc/rfc3766.txt>.

15. RFC 2104: HMAC: Keyed-Hashing for Message Authentication <http://www.ietf.org/rfc/rfc2104.txt>.

16. Recommendation for Block Cipher Modes of Operation: Federal Information Processing Standards Publication 800-38a <http://csrc.nist.gov/publications/ nistpubs/800-38a/sp800-38a.pdf>.

17. Although counter mode encryption requires no padding, implementations MAY still disguise the length of m by appending a random number of white-space characters.

18. If Bob were to receive a stanza out-of-order, then he would fail to decrypt the stanza and be forced to terminate the ESession.

19. If Bob were to receive a stanza out-of-order, then the MACs would not match because the values of CA would not be synchronized.

20. Bob MUST NOT send a stream error to his server since intermediate entities are not responsible for encoded content.

21. If an entity fails to receive any stanza that includes a new key in the correct order, then it will fail to decrypt the next stanza it receives and be forced to terminate the ESession.

22. Content is specified for the <terminate/> element to facilitate XML Normalization.

23. Canonical XML 1.0 <http://www.w3.org/TR/xml-c14n>.

24. RFC 3447: Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications Version 2.1 <http://www.ietf.org/rfc/rfc3447.txt>.

25. Digital Signature Standard: Federal Information Processing Standards Publication 186 <http://csrc.nist.gov/publications/fips/fips186-2/fips186-2-change1.pdf>.

26. RFC 1750: Randomness Recommendations for Security <http://www.ietf.org/rfc/rfc1750.txt>.

27. RFC 4344: SSH Transport Layer Encryption Modes <http://www.ietf.org/rfc/rfc4344.txt>.

28. IANA registry of parameters related to secure shell <http://www.iana.org/assignments/ssh-parameters>.

29. Advanced Encryption Standard: Federal Information Processing Standards Publication 197 <http://csrc.nist.gov/publications/fips/fips197/fips-197.pdf>.

30. The Twofish Block Cipher <http://www.schneier.com/twofish.html>.

31. The Serpent Block Cipher <http://www.cl.cam.ac.uk/~rja14/serpent.html>.

32. X.509 Authentication in SSH2 <http://www.ietf.org/internet-drafts/draft-ietf-secsh-x509-03.txt>. Work in progress.

33. Secure Hash Standard: Federal Information Processing Standards Publication 180-2 <http://csrc.nist.gov/publications/fips/fips180-2/fips186-2withchangenotice.pdf>.

34. The Whirlpool Hash Function <http://paginas.terra.com.br/informatica/paulobarreto/WhirlpoolPage.html>.

35. Standard ECMA-151: Data Compression for Information Interchange - Adaptive Coding with Embedded Dictionary - DLCZ Algorithm <http://www.ecma-international.org/publications/standards/Ecma-151.htm>.

36. RFC 1950: ZLIB Compressed Data Format Specification version 3.3 <http://www.ietf.org/rfc/rfc1950.txt>.

37. The Internet Assigned Numbers Authority (IANA) is the central coordinator for the assignment of unique parameter values for Internet protocols, such as port numbers and URI schemes. For further information, see <http://www.iana.org/>.

38. The Jabber Registrar maintains a list of reserved Jabber protocol namespaces as well as registries of parameters used in the context of protocols approved by the Jabber Software Foundation. For further information, see <http://www.jabber.org/registrar/>.

39. JEP-0068: Field Data Standardization for Data Forms <http://www.jabber.org/jeps/jep-0068.html>.

40. JEP-0013: Flexible Offline Message Retrieval <http://www.jabber.org/jeps/jep-0013.html>.

Version 0.10 (2006-07-18)

Version 0.9 (2005-11-29)

Version 0.8 (2005-09-27)

Version 0.7 (2005-08-26)

Version 0.6 (2005-08-12)

Version 0.5 (2005-08-10)

Version 0.4 (2005-08-09)

Version 0.3 (2005-08-02)

Version 0.2 (2004-07-26)

Version 0.1 (2003-09-09)