IETF Logo Mail Archive

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

bmanning@vacation.karoshi.com Tue, 08 March 2011 17:39 UTC

Return-Path: <bmanning@karoshi.com>
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 E33653A68AF for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 09:39:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 9u2o1zI5Dcjq for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 09:39:16 -0800 (PST)
Received: from vacation.karoshi.com (vacation.karoshi.com [198.32.6.68]) by core3.amsl.com (Postfix) with ESMTP id 19F953A68DC for <keyassure@ietf.org>; Tue, 8 Mar 2011 09:39:11 -0800 (PST)
Received: from karoshi.com (localhost.localdomain [127.0.0.1]) by vacation.karoshi.com (8.12.8/8.12.8) with ESMTP id p28Hdd7s025557; Tue, 8 Mar 2011 17:39:56 GMT
Received: (from bmanning@localhost) by karoshi.com (8.12.8/8.12.8/Submit) id p28HdTGW025550; Tue, 8 Mar 2011 17:39:29 GMT
Date: Tue, 08 Mar 2011 17:39:24 +0000
From: bmanning@vacation.karoshi.com
To: Paul Hoffman <paul.hoffman@vpnc.org>
Message-ID: <20110308173924.GB23708@vacation.karoshi.com.>
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> <4D7658AA.9010003@vpnc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D7658AA.9010003@vpnc.org>
User-Agent: Mutt/1.4.1i
Cc: keyassure@ietf.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 17:39:17 -0000

On Tue, Mar 08, 2011 at 08:26:18AM -0800, Paul Hoffman wrote:
> 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.

	and what are those reasons?

--bill

> 
> It's all headology, unfortunately.
> 
> --Paul Hoffman
> _______________________________________________
> keyassure mailing list
> keyassure@ietf.org
> https://www.ietf.org/mailman/listinfo/keyassure

v2.23.0 | Report a Bug | By Email