IETF Logo Mail Archive

Re: [keyassure] Opening issue #21: "Need to specify which crypto

"George Barwood" <george.barwood@blueyonder.co.uk> Tue, 08 March 2011 10:23 UTC

Return-Path: <george.barwood@blueyonder.co.uk>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3568D3A6836 for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 02:23:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.715
X-Spam-Level:
X-Spam-Status: No, score=0.715 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HELO_EQ_BLUEYON=1.4, MIME_BASE64_BLANKS=0.041, MIME_BASE64_TEXT=1.753]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qWwqiLtz1LnK for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 02:22:58 -0800 (PST)
Received: from smtp-out4.blueyonder.co.uk (smtp-out4.blueyonder.co.uk [195.188.213.7]) by core3.amsl.com (Postfix) with ESMTP id 364333A6821 for <keyassure@ietf.org>; Tue, 8 Mar 2011 02:22:58 -0800 (PST)
Received: from [172.23.170.147] (helo=anti-virus03-10) by smtp-out4.blueyonder.co.uk with smtp (Exim 4.52) id 1Pwu5I-000854-3j; Tue, 08 Mar 2011 10:24:08 +0000
Received: from [92.238.99.235] (helo=GeorgeLaptop) by asmtp-out4.blueyonder.co.uk with smtp (Exim 4.72) (envelope-from <george.barwood@blueyonder.co.uk>) id 1Pwu5E-0001lg-Ct; Tue, 08 Mar 2011 10:24:04 +0000
Message-ID: <C242929AA67E44778826521B22FE5ECF@local>
From: George Barwood <george.barwood@blueyonder.co.uk>
To: Ben Laurie <benl@google.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
References: <4D752197.5090403@vpnc.org><E1PwoBp-00079A-ED@login01.fos.auckland.ac.nz> <AANLkTi=wUn81yObiHfxpN6DT3Pv1EZDrAi5HGNC+nUv1@mail.gmail.com>
Date: Tue, 08 Mar 2011 10:24:02 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: base64
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5931
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Cc: keyassure@ietf.org, paul.hoffman@vpnc.org
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Mar 2011 10:23:02 -0000

----- Original Message ----- 
From: "Ben Laurie" <benl@google.com>
To: "Peter Gutmann" <pgut001@cs.auckland.ac.nz>
Cc: <keyassure@ietf.org>; <paul.hoffman@vpnc.org>
Sent: Tuesday, March 08, 2011 9:06 AM
Subject: Re: [keyassure] Opening issue #21: "Need to specify which crypto


On 8 March 2011 04:06, Peter Gutmann <pgut001@cs.auckland.ac.nz> wrote:
> Paul Hoffman <paul.hoffman@vpnc.org> writes:

> Don't really see the point of SHA-384 myself, but I'm not particularly opposed to its inclusion.

SHA-384 is faster to compute than SHA-256 on 64-bit machines, and has a bigger margin of security.

It's cheap to include it now, and avoids a potential big headache if/when SHA-256 proves to be vulnerable.

That doesn't seem very likely in the near future, but history indicates that we shouldn't be too confident.

By the same argument SHA-512 could also be defined, even if we don't expect to use it any time soon.

There is a reason NIST defined these functions ( even if as non-specialists we may not fully understand ).

v2.23.0 | Report a Bug | By Email