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

Martin Rex <mrex@sap.com> Tue, 08 March 2011 16:56 UTC

Return-Path: <mrex@sap.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 0243B3A67FB for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 08:56:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.221
X-Spam-Level:
X-Spam-Status: No, score=-10.221 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 dNvFYuuu83AZ for <keyassure@core3.amsl.com>; Tue, 8 Mar 2011 08:56:24 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id EAF523A67E7 for <keyassure@ietf.org>; Tue, 8 Mar 2011 08:56:23 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p28GvZ2C019811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 8 Mar 2011 17:57:35 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201103081657.p28GvYwq001089@fs4113.wdf.sap.corp>
To: nweaver@icsi.berkeley.edu
Date: Tue, 08 Mar 2011 17:57:34 +0100
In-Reply-To: <B99194C1-6A2F-4378-835D-4E1096FB095A@icsi.berkeley.edu> from "Nicholas Weaver" at Mar 8, 11 08:10:21 am
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
X-SAP: out
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
Reply-To: mrex@sap.com
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:56:25 -0000

Nicholas Weaver wrote:
> 
> I still don't get why SHA-384 instead of SHA-512.
> SHA-384 just seems silly to me: its no FASTER than SHA-512,
> it MUST be less secure than SHA-512.

There is no reason to this (in the sense of reasonable explanation).

It fosters on the premise that SHA-1 is completely and throroughly
broken and SHA-256 impaired by more serious attacks than currently
known for SHA-1 _long_ before a SHA-3 finalist is selected.


The only two situations, where *I* believe that having more than
one mandatory to implement hash algorithms for DANE would make sense:

  1)  when SHA-1 was permitted (which no one seems to be asking for)
  2)  when the SHA-3 winner has been determined (which hasn't happened yet)


Personally, I would strongly prefer the hash algorithm list for
DANE to be

   1)   SHA-256      (FIPS 180-3)    MUST implement
   2)   SHA-512      (FIPS 180-3)    SHOULD implement


Personally, I believe that SHA-384, and more so SHA-224 should have
never been defined by NIST, because they constantly confuse the
crypto-clueless about the purpose of these algorithms and cause
needless discussions.


-Martin