Re: [pkix] Straw-poll on OCSP responses for non-revoked certificates.

Tom Ritter <tom@ritter.vg> Wed, 31 October 2012 02:29 UTC

Return-Path: <tom@ritter.vg>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C71221F85EA for <pkix@ietfa.amsl.com>; Tue, 30 Oct 2012 19:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.976
X-Spam-Level:
X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGb3uJYGNeco for <pkix@ietfa.amsl.com>; Tue, 30 Oct 2012 19:29:58 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id D58F821F85E7 for <pkix@ietf.org>; Tue, 30 Oct 2012 19:29:57 -0700 (PDT)
Received: by mail-vb0-f44.google.com with SMTP id fc26so1132773vbb.31 for <pkix@ietf.org>; Tue, 30 Oct 2012 19:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ritter.vg; s=vg; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PZ/qsUeY2Pwi9yyj+kYzTvxs1ksBNMlyUK0n9vSJ5d0=; b=PSha8x7lpaGB1wABOP6bESPJ2pfYwhcWignv/YxEZMBhvhQNGJIdDdjriaEQUbjywn tMVxCDtsgiYEiCR8LixfRcfnv9DFkAMq6pZzI2A9H6DIelJwgzTxF1TgDQDgZzrxqP6C mKeKb/Huto/P/F8UJyZbwq0d06UnJ9vPxH8E4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=PZ/qsUeY2Pwi9yyj+kYzTvxs1ksBNMlyUK0n9vSJ5d0=; b=AfFdhupd8DwJ3TpFMzJMJZy6dtQcT9yXSqyadiIppqTJa0+M8C/IGG2dpXhVwHOeJi A8zAyhxujYIQ96LSI5WZKy7YOKVaQMzrNqhRVn+NJmpBmpg/LcPU1CbBlyAT42m81mBt q5vtwu8ULTulOrE3KjxlOyOhYQR32NmFVf9kuJjYLvpOFukf9VuJz44RqTp2seWXm2Tm LcJ6QuUd471nTscRqAv7g+7NROtJ3ZKb2m4rUIaggrG6jLbg0AwVnbyLOcpKMQu3a7lN dNciezJ0ouXDuAB18K9jd2pUtbFu0B5AVwTHpD5YgfcN5ibVNSBQhcEKnPmqdslS1Iyy g60g==
MIME-Version: 1.0
Received: by 10.52.70.48 with SMTP id j16mr45657064vdu.1.1351650597227; Tue, 30 Oct 2012 19:29:57 -0700 (PDT)
Received: by 10.58.151.178 with HTTP; Tue, 30 Oct 2012 19:29:56 -0700 (PDT)
Received: by 10.58.151.178 with HTTP; Tue, 30 Oct 2012 19:29:56 -0700 (PDT)
In-Reply-To: <CCB55CA3.52588%stefan@aaa-sec.com>
References: <20121029232328.BF5D91A309@ld9781.wdf.sap.corp> <CCB55CA3.52588%stefan@aaa-sec.com>
Date: Tue, 30 Oct 2012 22:29:56 -0400
Message-ID: <CA+cU71=uV15awurem7Z-F7xTGp7E_U+NM9P2CjynMdFWbB6Fyg@mail.gmail.com>
From: Tom Ritter <tom@ritter.vg>
To: Stefan Santesson <stefan@aaa-sec.com>
Content-Type: multipart/alternative; boundary="20cf307f3996b54c9604cd51ad1b"
X-Gm-Message-State: ALoCoQlTaiNMLG+dQyaImIlGLTk1YLDOWg7juJ6/0yWN1ahvRAbd32Y+siR6pUYkQKHXqrlq4hBb
Cc: pkix@ietf.org
Subject: Re: [pkix] Straw-poll on OCSP responses for non-revoked certificates.
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PKIX Working Group <pkix.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pkix>, <mailto:pkix-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pkix>
List-Post: <mailto:pkix@ietf.org>
List-Help: <mailto:pkix-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pkix>, <mailto:pkix-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Oct 2012 02:29:59 -0000

1
On Oct 30, 2012 7:05 AM, "Stefan Santesson" <stefan@aaa-sec.com> wrote:

> Before we loose everyone engaged in this, I would like to make a
> straw-poll:
>
>
> Background:
> A client may do a request for a certificate that has never been issued by
> the CA.
> This request may be done deliberately, by mistake or as a consequence of a
> compromised CA.
>
> The OCSP protocol does not require OCSP responders to have any knowledge
> about issued certificates. It must only know about revoked certificates
> that are within it's current validity period. However, some OCSP
> responders closely coupled with the CA may also know if a certificate with
> a particular serialNumber value has been issued or not.
>
> The following is agreed:
>    - An OCSP responder is allowed to respond "good" to a status request
> for a non-revoked certificate, disregarding if it has ever been issued.
>
>    - A client, having no additional out-of-band knowledge about the OCSP
> responder, will just know that the certificate is "not revoked" when
> receiving a "good" response, unless the response includes one or more
> response extensions that provides additional information.
>
>
> The following is debated:
>    - Is an OCSP responder allowed to respond "revoked" even if a requested
> certificate serial number is not on the list of revoked certificates, IF
> the OCSP responder has positive knowledge that the requested serial number
> does NOT represent a valid certificate issued by the identified CA?
>
>
> Rationale for:
> There are a number of reasons to allow this that has been mentioned, such
> as:
>  - It breaks nothing. A legitimate request for an issued certificate will
> get a legitimate deterministic response.
>  - It's safer. Responding "revoked" may not prevent a compromised CA from
> being exploited. But if a request for a serialNumber that is known to be
> bad is done nevertheless, a "revoked" response will at least be safer than
> responding "good".
>  - Allowing extension definitions with further semantics. A response
> extension may be defined in the future that adds more information about
> the requested certificate. This may include a positive confirmation that
> the certificate has been issued as well as information that this
> particular OCSP responder will only respond "good" if it knows that the
> requested certificate has been issued, otherwise it will respond
> "revoked". An extension with such semantics can only be defined if the
> base standard allows a status other than "good" in such situation.
>  - Supporting Web-PKI. The CAB-Forum has indicated that they will profile
> the OCSP protocol for use with web server authentication. In such profile
> they have indicated that they will NOT allow the "good" response unless
> the requested certificate is known to have been issued. This means that
> they will require OCSP responder in their infrastructure to have this
> knowledge. Such profile would have to break the base OCSP standard if this
> states that "good" MUST be returned unless the certificate has been
> revoked.
>
> Rationale against:
> The basic rationale against raised on this list has been the argument that
> it is wrong and confusing to allow anything but "good" as a response to a
> non-revoked certificate (if the cert is issued by a CA that is served by
> this OCSP responder).
> Another strong opinion is that it basically does not solve anything. A
> broken CA is broken and can't be fixed by responding "revoked". It would
> be easy to adapt an attack to circumvent such response, for example by
> issuing a fake certificate that duplicates a legitimate serialNumber.
>
>
> Please reply with either:
>
> 1. Allow "revoked" response for a certificate that has not been "revoked"
> but where that OCSP responder for any other reason knows the certificate
> to be "bad".
>
> 2. Require that the OCSP responder MUST respond "good" in this situation.
>
> 3. Neither 1 or 2 (motivate).
>
>
>
>
> Note: both alternatives are placed in a context where the certificate is
> claimed to be issued by a CA that is served by this OCSP responder. The
> exact meaning of "bad" is for later discussion.
>
> Please keep any motivation short and do not use this thread for long
> debates.
>
>
>
>
>
>
> _______________________________________________
> pkix mailing list
> pkix@ietf.org
> https://www.ietf.org/mailman/listinfo/pkix
>