IETF Logo Mail Archive

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

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 08 March 2011 16:25 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 BE5BC3A691E for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 08:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.911
X-Spam-Level:
X-Spam-Status: No, score=-101.911 tagged_above=-999 required=5 tests=[AWL=0.688, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 1qdfhwC7jX+Q for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 08:25:04 -0800 (PST)
Received: from hoffman.proper.com (unknown [IPv6:2001:4870:a30c:41::81]) by core3.amsl.com (Postfix) with ESMTP id 837BC3A68F8 for <keyassure@ietf.org>; Tue, 8 Mar 2011 08:25:04 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p28GQIrK039129 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Tue, 8 Mar 2011 09:26:18 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D7658AA.9010003@vpnc.org>
Date: Tue, 08 Mar 2011 08:26:18 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: keyassure@ietf.org
References: <397794924.536913.1299565388720.JavaMail.root@cm-mail03.mozilla.org> <E971C167-FE76-497D-A156-16EF687B522A@kirei.se> <4D765239.40408@ieca.com> <B99194C1-6A2F-4378-835D-4E1096FB095A@icsi.berkeley.edu>
In-Reply-To: <B99194C1-6A2F-4378-835D-4E1096FB095A@icsi.berkeley.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 16:25:05 -0000

On 3/8/11 8:10 AM, Nicholas Weaver wrote:
> (Not that I'm saying it should impede this group, I'm happing with the language above or similar, I just want to know why people want to use SHA-384 instead of SHA-512!)

There is some reason to believe that the final SHA-3 spec will have a 
384-bit hash that will be faster to calculate than the 512-bit version, 
and it will be hard to convince people who were using SHA-2-512 that 
going to SHA-3-384 is a good move. They'll claim that it is less safe 
because they didn't realize that they didn't even need the strength in 
SHA-2-256 to start with.

It's all headology, unfortunately.

--Paul Hoffman

v2.23.0 | Report a Bug | By Email