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

Martin Rex <mrex@sap.com> Wed, 02 March 2011 15:28 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 56DF23A680F for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 07:28:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.234
X-Spam-Level:
X-Spam-Status: No, score=-10.234 tagged_above=-999 required=5 tests=[AWL=0.015, 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 ni3+VKSVMhqL for <keyassure@core3.amsl.com>; Wed, 2 Mar 2011 07:28:11 -0800 (PST)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id 54ACF3A67D0 for <keyassure@ietf.org>; Wed, 2 Mar 2011 07:28:11 -0800 (PST)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id p22FTF6X004553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 2 Mar 2011 16:29:15 +0100 (MET)
From: Martin Rex <mrex@sap.com>
Message-Id: <201103021529.p22FTFOu002845@fs4113.wdf.sap.corp>
To: mrex@sap.com
Date: Wed, 2 Mar 2011 16:29:15 +0100 (MET)
In-Reply-To: <201103020150.p221owI6017784@fs4113.wdf.sap.corp> from "Martin Rex" at Mar 2, 11 02:50:58 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-SAP: out
Cc: hallam@gmail.com, 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: Wed, 02 Mar 2011 15:28:12 -0000

Martin Rex wrote:
> 
> And there are still a number of TrustAnchors in every Browser that
> carry an md5WithRsaEncryption signature.
> 
> But it's actually worse than that -- VeriSign still has a CA cert
> in service with an md2WithRsaEncryption -- and is still using it
> productively (check https://www.hp.com/).

I'm terribly sorry, I mixed up the (by now long) list of VeriSign
RootCA certs.

The RootCA cert under which the server cert for https://www.hp.com
is "VeriSign Class 3 Public Primary Certification Authority - G2"
and uses sha1WithRsaEncryption.  But it still is an X.509v1 cert.

My Firefox 3.5.13 comes with these three VeriSign RooCA certs
that are X.509v1, use md2WithRsaSignature and valid until 02-Aug-2028:

   "VeriSign Class 1 Public Primary Certification Authority"
   "VeriSign Class 2 Public Primary Certification Authority"
   "VeriSign Class 3 Public Primary Certification Authority"
   

-Martin