IETF Logo Mail Archive

Re: [saag] Revision of "Attacks on Cryptographic Hashes in Internet Protocols"

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 14 November 2012 04:24 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3CC21F84CE for <saag@ietfa.amsl.com>; Tue, 13 Nov 2012 20:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8gaMO+-3o27U for <saag@ietfa.amsl.com>; Tue, 13 Nov 2012 20:24:23 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 57EF221F84C7 for <saag@ietf.org>; Tue, 13 Nov 2012 20:24:21 -0800 (PST)
Received: from wsip-24-120-140-174.lv.lv.cox.net (wsip-24-120-140-174.lv.lv.cox.net [24.120.140.174]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id qAE4OFot095546 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Nov 2012 21:24:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <50A2C6A3.7090700@isi.edu>
Date: Tue, 13 Nov 2012 20:24:19 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4D22742-9874-463D-B175-DAB9DCC5BC89@vpnc.org>
References: <9B93EFAD-AD9B-4402-8CC2-79239EB3DF2E@vpnc.org> <50A2C6A3.7090700@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.1499)
Cc: IETF Security Area Advisory Group <saag@ietf.org>
Subject: Re: [saag] Revision of "Attacks on Cryptographic Hashes in Internet Protocols"
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Nov 2012 04:24:23 -0000

On Nov 13, 2012, at 2:16 PM, Joe Touch <touch@isi.edu> wrote:

> This doc refers to IETF protocols that use hashes, but doesn't discuss any in specific. It also doesn't address how hashes are used, e.g., solo (as a fingerprint), keyed (for authentication and source confirmation), as part of an HMAC, or as part of key derivation.
> 
> That sort of information might be additionally useful, IMO.

The opposite was decided when we did RFC 4270, of which this is a direct revision. Many protocols use hashes in multiple ways, and trying to list them was considered a distraction. I believe that is still the case.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email