Dialback Key Generation and Validation

%ents; ]>

Dialback Key Generation and Validation This document provides a recommended method for generating and validating the keys used in the XMPP server dialback protocol. &LEGALNOTICE; 0185 Proposed Informational Standards Council XMPP Core N/A Philipp Hancke fippo@goodadvice.pages.de fippo@goodadvice.pages.de 0.3 ph 2006-11-01

Recommended hashing the secret to satisfy length requirement; hostnames and Stream ID should be separated by spaces to avoid ambiguity; updated example to match rfc3920bis.

0.2 ph 2006-05-10

Clarified and corrected roles of originating and receiving servers; updated recommendation and main example to use HMAC-SHA256 for key generation.

0.1 2006-04-11 psa

Initial version.

0.0.1 2006-03-30 ph

First draft.

&RFC3920BISNOTE;

RFC 3920 does not specify in detail how to generate the keys used in the server dialback protocol, and why each of the variables used in key generation is crucial for security. This document is provided for discussion purposes and aims at clarifying the key generation and its validation mechanism and to show common attacks on weak mechanisms. It is not meant to supersede the text in RFC 3920; however, the recommendations in this document have been incorporated into rfc3920bis.

The Originating Server, which generates the dialback key, and the Authoritative Server, which validates the dialback key, may reside on different hosts or be running in separate processes. The method used in key generation and validation should not require interactive communication between Originating Server, Authoritative Server and optionally a third party like a database.

The key is generated based on:

the (hostname of) Originating Server,
the (hostname of) Receiving Server,
the Stream ID,
and a secret known by the Authoritative Server's network.

The last item, a shared secret known to Originating Server and Authoritative Server, is used in a Keyed-Hash Message Authentication Code (HMAC) to generate and validate the dialback keys. This key must either be set up in a configuration option for each host or process, or generated as a random string when starting the server.

&nistfips198a; recommends that the length of the key should be at least half the size of the hash function output. To fulfill this requirement, the secret SHOULD be hashed with the hash function prior to usage as a key in HMAC.

The Stream ID and the involved hostnames should be concatenated with a unicode space character (U+0020) for the delimiter.


key = HEX( HMAC-SHA256( SHA256(Secret), { Receiving Server, ' ', 
		    Originating or Authoritative server, ' ', Stream ID } ) )

To avoid problems of encoding, a hexadecimal representation of the digest algorithm output SHOULD be used.

This document closely follows the description of the dialback protocol in RFC 3920, but omits steps that are not important for the generation and validation of the dialback keys. For ease of comparison the numbering of the steps is the same as in section 8.3 of RFC 3920. Any line breaks in the examples are included for the purpose of readability only.

The following data values are used in the examples:

Originating and Authoritative Server	example.com
Receiving Server	example.net
Secret	s3cr3tf0rd14lb4ck
Stream ID	D60000229F

3. Receiving Server sends a stream header back to the Originating Server, including a unique ID for this interaction:

]]>

The Originating Server now generates a dialback key to be sent to the Receiving Server:


key = HMAC-SHA256( 
                   SHA256(secret), 
                   { Receiving server, ' ', Originating server, ' ', Stream ID}
                 )
    = HMAC-SHA256( 
                   SHA256('s3cr3tf0rd14lb4ck'), 
                   { 'example.net', ' ', 'example.com', ' ', 'D60000229F' }
                 )
    = HMAC-SHA256( 
                   'a7136eb1f46c9ef18c5e78c36ca257067c69b3d518285f0b18a96c33beae9acc', 
                   'example.net example.com D60000229F'
                 )
    = '008c689ff366b50c63d69a3e2d2c0e0e1f8404b0118eb688a0102c87cb691bdc'

4. The Originating Server sends the generated dialback key to the Receiving Server:


    008c689ff366b50c63d69a3e2d2c0e0e1f8404b0118eb688a0102c87cb691bdc

    ]]>

8. The Receiving Server sends the Authoritative Server a request for verification of the key:


    008c689ff366b50c63d69a3e2d2c0e0e1f8404b0118eb688a0102c87cb691bdc

    ]]>

The Authoritative Server calculates the valid key for this verify request, using data supplied in the packet and the secret shared with the Originating Server.


key = HMAC-SHA256( 
                   secret, 
                   { Receiving Server, ' ', Authoritative Server, ' ', Stream ID }
                 )
    = HMAC-SHA256( 
                   SHA256('s3cr3tf0rd14lb4ck'), 
                   { 'example.net', ' ', 'example.com', ' ', 'D60000229F' }
                 )
    = HMAC-SHA256( 
                    'a7136eb1f46c9ef18c5e78c36ca257067c69b3d518285f0b18a96c33beae9acc', 
                    'example.net example.com D60000229F'
                  )
    = '008c689ff366b50c63d69a3e2d2c0e0e1f8404b0118eb688a0102c87cb691bdc'

9. The Authoritative Server compares this value to the key contained in the verification requests and informs the Originating Server of the result, in our example a success:

]]>

This section contains attack scenarios that illustrate why each of the factors used in key generation is important.

An attacker will assume the role of the Originating Server and try to send a dialback key that the Authoritative Server acknowledges as valid. If this is successful, the attacker is allowed to send packets for the hostname of the Authoritative Server.

In each subsection, the example hash method, which uses the (compromised and NOT RECOMMENDED) SHA1 algorithm as described in &rfc3174; for simplicity, ignores one of the variables,

Originating Server,
Stream ID,
Receiving Server,
or Secret,

and it is shown how an attacker might exploit this behavior to get a valid result from the Authoritative Server.

This subsection demonstrates what can happen if the key generation method ignores the hostname of the Originating Server, e.g. for the hash function


key = SHA1({ Secret, Receiving Server, Stream ID })

The dialback keys generated for the originating domains 'example.com' and 'example.net' are the same, which might disclose that the secret used to generate the keys for these domains is equal. An attacker cannot exploit this any further.

 
    dba68f5de5b1766d55e70109f42842695bdeb6e4

    ]]>

This key is generated using:


SHA1('s3cr3tf0rd14lb4ckexample.netD60000229F') = 
	    'dba68f5de5b1766d55e70109f42842695bdeb6e4'

This subsection demonstrates a replay attack that is possible if the key generation method ignores the Stream ID, e.g. for the hash function


key = SHA1({ Secret, Receiving Server, Originating Server })

If the attacker is able to obtain a single valid dialback key exchanged between the two domains, this key can be used to validate any stream.

 
    48337750828778765f5e2abbce14a6c5680f2fff

    ]]>

This key is generated using the empty string instead of the id:


SHA1('s3cr3tf0rd14lb4ckexample.netexample.com') = 
	    '48337750828778765f5e2abbce14a6c5680f2fff'

This key is also valid for


    48337750828778765f5e2abbce14a6c5680f2fff

    ]]>

This subsection demonstrates against a key generation method that ignores the hostname of the receiving server, e.g. for the hash function


key = SHA1({ Secret, Originating Server, Stream ID })

The attacker can use a dialback key and stream ID we have sent to a domain under his control.

 
    eb6c42adee0ced8782175f98a56e4c00b2503602

    ]]>

This key is generated using:


SHA1('s3cr3tf0rd14lb4ckexample.comD60000229F') = 
	    'eb6c42adee0ced8782175f98a56e4c00b2503602'

If the key generation method does not take into account a shared secret in the Authoritative Servers network or if this secret is disclosed and the key generation method is known, an attacker can generate valid dialback keys.


key = SHA1({ Receiving Server, Originating Server, Stream ID })

In both cases the attacker is able to generate an arbitrary number of dialback keys.

 
    c08b18d349a9c4d6aaca2dc3baa772bb7749e3b8

    ]]>

This key is generated using:


SHA1('example.netexample.comD60000229F') = 
	    'c08b18d349a9c4d6aaca2dc3baa772bb7749e3b8'

This document introduces no security considerations or concerns above and beyond those discussed in RFC 3920, but describes what might happen if the security considerations are ignored.

This document requires no interaction with &IANA;.

This document requires no interaction with the ®ISTRAR;.

Thanks to Ian Paterson and Matthias Wimmer for their feedback.