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

Martin Rex <mrex@sap.com> Tue, 01 March 2011 18:14 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 E099A3A698E for <keyassure@core3.amsl.com>; Tue, 1 Mar 2011 10:14:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.233
X-Spam-Level:
X-Spam-Status: No, score=-10.233 tagged_above=-999 required=5 tests=[AWL=0.016, 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 Gk3A5yz9bEJ0 for <keyassure@core3.amsl.com>; Tue, 1 Mar 2011 10:14:55 -0800 (PST)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by core3.amsl.com (Postfix) with ESMTP id DE1C23A6957 for <keyassure@ietf.org>; Tue, 1 Mar 2011 10:14:54 -0800 (PST)
Received: from mail.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id p21IFuSa014735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 1 Mar 2011 19:15:56 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201103011815.p21IFukr020670@fs4113.wdf.sap.corp>
To: hallam@gmail.com (Phillip Hallam-Baker)
Date: Tue, 1 Mar 2011 19:15:56 +0100 (MET)
In-Reply-To: <AANLkTimGsc38B+2R03CiW2TzKoiHvj_7NLs0gD=340Tw@mail.gmail.com> from "Phillip Hallam-Baker" at Feb 25, 11 04:52:06 pm
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, 01 Mar 2011 18:14:56 -0000

Phillip Hallam-Baker wrote:
> 
> Currently, the only digest algorithm that can be recommended is SHA-2
> 
> We really do need SHA2 in here as a MUST, unless we are still discussing
> this when the SHA3 competition results are out.

SHA-256 looks like plenty.

You do realize, that many (if not most) implementations of TLS are going
to use SHA-1 for digital signatures for quite some time to come?

And even document like the updated TLS extensions document (rfc6066)
use SHA-1 all over the place.

-Martin