Re: Online Certificate Revocation Protocol

pgut001@cs.auckland.ac.nz (Peter Gutmann) Sun, 10 June 2001 12:36 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA10352 for <pkix-archive@odin.ietf.org>; Sun, 10 Jun 2001 08:36:25 -0400 (EDT)
Received: from localhost (localhost [[UNIX: localhost]]) by above.proper.com (8.11.3/8.11.3) id f5ABkQC17217 for ietf-pkix-bks; Sun, 10 Jun 2001 04:46:26 -0700 (PDT)
Received: from mail.ec.auckland.ac.nz (mail.student.auckland.ac.nz [130.216.35.201]) by above.proper.com (8.11.3/8.11.3) with ESMTP id f5ABkNJ17208 for <ietf-pkix@imc.org>; Sun, 10 Jun 2001 04:46:23 -0700 (PDT)
Received: from kahu.cs.auckland.ac.nz (pgut001@kahu.cs.auckland.ac.nz [130.216.36.13]) by mail.ec.auckland.ac.nz (8.9.3/8.8.6/cs-master) with SMTP id XAA05091; Sun, 10 Jun 2001 23:46:21 +1200 (NZST) (sender pgut001@cs.auckland.ac.nz)
Received: by kahu.cs.auckland.ac.nz (relaymail v0.9) id <99217358114998>; Sun, 10 Jun 2001 23:46:21 (NZST)
From: pgut001@cs.auckland.ac.nz
To: pgut001@cs.auckland.ac.nz, rhousley@rsasecurity.com
Subject: Re: Online Certificate Revocation Protocol
Cc: ietf-pkix@imc.org
Reply-To: pgut001@cs.auckland.ac.nz
X-Charge-To: pgut001
X-Authenticated: relaymail v0.9 on kahu.cs.auckland.ac.nz
Date: Sun, 10 Jun 2001 23:46:21 -0000
Message-ID: <99217358114998@kahu.cs.auckland.ac.nz>
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>
List-ID: <ietf-pkix.imc.org>

"Housley, Russ" <rhousley@rsasecurity.com> writes:

>You make an interesting point.  I figure that a message signed with the 
>private key that is claiming to be compromised is a good thing to pay 
>attention to.
>
>If the message is from the subscriber, then that subscriber probably knows 
>that some bad thing just happened and the subscriber is trying to let 
>everyone know.  He does not want any one to rely on the key any more.
>
>If the message is not from the subscriber, then the key has absolutely been 
>compromised.  What a nice attacker to tell everyone.
 
It's not necessarily as simple as that, for example if you have an 
encryption-only key (no way to revoke your cert if you need to submit a signed 
request) or if you've lost your private key (or it was physically stolen), or 
whatever there's nothing you can do if your CA follows the DOS model.  Having 
an attacker notify everyone of revocation is also perfectly possible, if I 
steal your key I'll submit a revocation for the once-a-day affiliation-changed 
CRL to prevent you from putting it on the 15-minute key-compromise CRL and 
guarantee me a full day to do whatever I want with it.
 
Peter.