From 77a742dc3e3230f6b99487ce39a0e7d9cda216b0 Mon Sep 17 00:00:00 2001 From: stpeter Date: Thu, 16 Jun 2011 13:10:01 -0600 Subject: [PATCH] 0.0.1 --- inbox/hashes.xml | 134 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 134 insertions(+) create mode 100644 inbox/hashes.xml diff --git a/inbox/hashes.xml b/inbox/hashes.xml new file mode 100644 index 00000000..cf6553d1 --- /dev/null +++ b/inbox/hashes.xml @@ -0,0 +1,134 @@ + + +%ents; +]> + + +
+ Use of Cryptographic Hash Functions in XMPP + This document provides recommendations for the use of cryptographic hash functions in XMPP protocol extensions. + &LEGALNOTICE; + XXXX + ProtoXEP + Standards Track + Standards + Council + + XMPP Core + + + + N/A + &stpeter; + + 0.0.1 + 2011-06-16 + psa +

Rough draft based on list discussion.

 + +
+ + +

Various XMPP extensions make use of cryptographic hash functions, but they do so in different ways (e.g., some define XML elements and some define XML attributes) and often mandate support for different algorthms (e.g., &xep0096; uses MD5, &xep0115; uses SHA-1, and &xep0116; used SHA-256). The lack of a consistent approach to the use of cryptographic hash functions in XMPP extensions can lead to interoperability problems and security vulnerabilities. Therefore, this document recommends a common approach and XML element that can be re-used in any XMPP protocol extension.

+ + + +

This extension is designed to meet the following criteria:

+
+
Agility
It is absolutely necessary to support more secure cryptographic hash functions as they become available, and to stop supporting less secure functions as they are deprecated.
 +
Security
This document needs to be regularly maintained and revisited so that XMPP protocols are using the most up-to-date security technologies.
 +
Reusability
The extension needs to be reusable in any XMPP protocol.
 +
+ + + +

This document defines a new XML element that can be used in any XMPP protocol extension. An example follows.

+ + 2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU= + + ]]> +

The value of the 'algo' attribute MUST be one of the values from the &ianahashes; maintained by &IANA;.

+ + + +

This document defines the XML namespace 'urn:xmpp:hashes:0'. The document MUST be updated, and the namespace version MUST be incremented, whenever the XSF wishes to modify the list of mandatory, recommended, deprecated, and obsolete algorithms.

+ + + + +

The MD2 algorithm is not used in any XMPP protocols and has been deprecated by the IETF (see &rfc6149;).

+ + +

The MD4 algorithm is not used in any XMPP protocols and has been deprecated by the IETF (see &rfc6150;).

+ + +

The MD5 algorithm is used in several XMPP protocols. As explained in &rfc6151;, the MD5 algorithm "is no longer acceptable where collision resistance is required" (such as in digital signatures) and "new protocol designs should not employ HMAC-MD5" either. The XSF is working to deprecate the use of MD5 in XMPP protocols.

+ + +

The SHA-0 algorithm was developed by the U.S. National Securitiy Agency and first published in 1993. It was never widely deployed and is not used in any XMPP protocols.

+ + +

The SHA-1 algorithm was developed by the U.S. National Security Agency and first published in 1995 to fix problems with SHA-0. The SHA-1 algorithm is currently the most widely-deployed hash function. As described in &rfc4270; in 2005, attacks have been found against the collision resistance property of SHA-1. &rfc6194; notes that no published results indicate improvement upon those attacks. In addition, RFC 6194 notes that "[t]here are no known pre-image or second pre-image attacks that are specific to the full round SHA-1 algorithm". However, the U.S. National Institute of Standards and Technology (NIST) has recommended that SHA-1 not be used for generating digital signatures after December 31, 2010. However, there is no indication that attacks on SHA-1 can be extended to HMAC-SHA-1.

+

The XSF is strongly encouraged to consider migrating its existing uses of SHA-1 to the SHA-2 family of algorithms, and to the SHA-3 family when available.

+ + +

The SHA-2 family of algorithms (SHA-224, SHA-256, SHA-384, and SHA-512) were developed by the U.S. National Security Agency and first published in 2001. Because SHA-2 is somewhat similar to SHA-1, it is thought that the security flaws with SHA-1 described above could be extended to SHA-2 (although no such attacks have yet been found on the full-round SHA-2 algorithms).

+ + +

The U.S. National Institute of Standards and Technology (NIST) is currently holding a public competition to replace the SHA-1 and SHA-2 functions. The winner and resulting new standard will be announced in 2012. When this "SHA-3" technology is announced, the XSF will update this specification accordingly.

+ + + + +

Support for version 0 of the 'urn:xmpp:hashes' namespace implies the following:

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
AlgorithmSupport
MD2MUST NOT
MD4MUST NOT
MD5MAY
SHA-1MUST
SHA-256MUST
SHA-512SHOULD
+

These recommendations ought to be reviewed yearly by the &COUNCIL;.

+ + + +

This entire document discusses security.

+ + + +

This document requires no interaction with the IANA. However, it reuses entries from the relevant IANA registry.

+ + + +

This document requires no interaction with the ®ISTRAR;.

+ + + +

Thanks to Dave Cridland, Waqas Hussain, Glenn Maynard, and Remko Tronçon for their input.

+ +