RE: OCSP Algorithm Agility

"Andrews, Rick" <RAndrews@verisign.com> Wed, 03 October 2007 20:17 UTC

Return-path: <owner-ietf-pkix@mail.imc.org>
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IdAfH-0001aE-1i for pkix-archive@lists.ietf.org; Wed, 03 Oct 2007 16:17:52 -0400
Received: from balder-227.proper.com ([192.245.12.227]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IdAf2-00019b-3I for pkix-archive@lists.ietf.org; Wed, 03 Oct 2007 16:17:37 -0400
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l93JTTRl014047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Oct 2007 12:29:29 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.13.5/8.13.5/Submit) id l93JTTe8014046; Wed, 3 Oct 2007 12:29:29 -0700 (MST) (envelope-from owner-ietf-pkix@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from robin.verisign.com (robin.verisign.com [65.205.251.75]) by balder-227.proper.com (8.13.5/8.13.5) with ESMTP id l93JTS4x014039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-pkix@imc.org>; Wed, 3 Oct 2007 12:29:28 -0700 (MST) (envelope-from RAndrews@verisign.com)
Received: from mou1wnexcn01.vcorp.ad.vrsn.com (mailer1.verisign.com [65.205.251.34]) by robin.verisign.com (8.12.11/8.13.4) with ESMTP id l93JR0XB008272; Wed, 3 Oct 2007 12:27:00 -0700
Received: from MOU1WNEXMB14.vcorp.ad.vrsn.com ([10.25.13.245]) by mou1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 3 Oct 2007 12:29:27 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: RE: OCSP Algorithm Agility
Date: Wed, 3 Oct 2007 12:29:26 -0700
Message-ID: <0D028BDBFBA58441BD8E9746914806422AE2D9@MOU1WNEXMB14.vcorp.ad.vrsn.com>
In-Reply-To: <82D5657AE1F54347A734BDD33637C87909439443@EXVS01.ex.dslextreme.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: OCSP Algorithm Agility
Thread-Index: Acf8l4NIxZexIh9rTveKgrEJmUDxVQAAJZEAAlba1eA=
From: "Andrews, Rick" <RAndrews@verisign.com>
To: "Santosh Chokhani" <chokhani@orionsec.com>, <ietf-pkix@imc.org>
X-OriginalArrivalTime: 03 Oct 2007 19:29:27.0625 (UTC) FILETIME=[B6732390:01C805F3]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by balder-227.proper.com id l93JTT4w014040
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1

Santosh,

Sorry for the long delay in responding - travel and vacation.
 
Not all OCSP responders work from CRLs, so they won't take their cue
from the CRL. Nor should they take their cue from the signature on the
cert in question, I believe. Let me try to restate my argument in a
different way.
 
With SCVP delegated path validation, the client requesting a cert's
status from an OCSP responder will be different from the client at the
other end of the SSL connection. Those two clients may have very
different capabilities in terms of supported signature and hash
algorithms. It's not realistic to expect that all SSL clients, all SCVP
servers, and all CAs will be able to upgrade in lockstep to new
algorithms as they are developed. Allowing the OCSP client and server to
negotiate a mutually-acceptable set of algorithms is essential to the
deployment of newer, stronger algorithms.
 
Likewise, companies that run large OCSP responders may wish to gradually
move to ECC-based signatures for all their OCSP responses, even those
for certs with RSA or DSA keys, because ECC signatures are cheaper to
produce. If algorithm agility is added to OCSP, those companies can
gradually achieve the move to ECC without disrupting the installed base
of OCSP clients that don't support ECC.
 
-Rick Andrews 

> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org] On Behalf Of Santosh Chokhani
> Sent: Friday, September 21, 2007 2:45 PM
> To: Paul Hoffman; Stephen Kent; ietf-pkix@imc.org
> Subject: RE: OCSP Algorithm Agility
> 
> 
> Paul,
> 
> Here are my views on this.
> 
> The client should be first asking for the algorithm suite 
> that signed the certificate in question.  There is no need 
> for the client to ask for anything stronger.  The client can 
> ask for stronger suites as secondary, if client has them.
> 
> In the scenario you cite, the Responder certificate will not 
> include RSA with SHA 1 any longer.  So, client will know that 
> Responder only supported his second choice and he should be 
> ok with it.
> 
> -----Original Message-----
> From: owner-ietf-pkix@mail.imc.org 
> [mailto:owner-ietf-pkix@mail.imc.org]
> On Behalf Of Paul Hoffman
> Sent: Friday, September 21, 2007 4:39 PM
> To: Stephen Kent; ietf-pkix@imc.org
> Subject: RE: OCSP Algorithm Agility
> 
> 
> At 2:07 PM -0400 9/21/07, Stephen Kent wrote:
> >How about defining an extension to be included in the cert 
> issued to an 
> >OCSP responder by a CA.  The extension would have an ordered list of 
> >algorithms (hash and signature if we want to address more 
> than the hash 
> >agility issue) accepted by the OCSP responder.  An OCSP 
> client can use 
> >this info to determine what is the "best" algorithm (or alg 
> pair) that 
> >it and the responder share. The combination of this extension and an 
> >OCSP negotiation procedure will allow the client to detect MITM 
> >downgrade attacks. In fact, if the client acquires the 
> responder's cert 
> >prior to making a request, there would not even be a need for real 
> >negotiation, since the client would know what alg to request in a 
> >response.
> 
> Imagine the list of algorithms is RSA-with-SHA1 first and
> DSA-with-SHA1 second. How does your negotiation work? The 
> client asks for this message to be signed with RSA-with-SHA1. 
> But the server knows that RSA-with-SHA1 has been compromised 
> since it got that certificate from the CA. What does the 
> server say to the client to indicate that it only wants to 
> sign with DSA-with-SHA1? What prevents Mallory from saying 
> the same thing to the client?
> 
> --Paul Hoffman, Director
> --VPN Consortium
> 
> 
>