Re: [TLS] Possible revocation delay issue with TLS stapling

Martin Rex <> Fri, 26 March 2010 21:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1CC233A6993 for <>; Fri, 26 Mar 2010 14:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.386
X-Spam-Status: No, score=-8.386 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_EQ_DE=0.35, J_CHICKENPOX_92=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id LisKczJTwLfi for <>; Fri, 26 Mar 2010 14:39:04 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id E9AB83A6895 for <>; Fri, 26 Mar 2010 14:39:03 -0700 (PDT)
Received: from by (26) with ESMTP id o2QLdQ6J005083 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Mar 2010 22:39:26 +0100 (MET)
From: Martin Rex <>
Message-Id: <>
To: (Yngve N. Pettersen)
Date: Fri, 26 Mar 2010 22:39:25 +0100 (MET)
In-Reply-To: <op.u95kjftmkvaitl@lessa-ii> from "Yngve N. Pettersen" at Mar 26, 10 03:15:05 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal07
X-SAP: out
Subject: Re: [TLS] Possible revocation delay issue with TLS stapling
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 26 Mar 2010 21:39:05 -0000

Yngve N. Pettersen wrote:
> While considering aspects of my multiple certificate status suggestions a
> few days ago I realized that TLS stapling (the TLS Certificate status
> Extension)of OCSP exacerbates the inherent "delay problem" when a
> certificate is revoked, depending on how long the OCSP response is valid.
> A malicious server that have its certificate revoked will still be able to
> use an old unexpired OCSP response in its stapled status reports to the
> clients for quite a while after the revocation, since the response will
> usually be valid for several days.

possible solutions:
  - define that clients should not accept OCSP responses sent
    within the handshake with the "producedAt" XX hours in the past
  - require servers to refresh their OCSP responses every XX hours
    so that "producedAt" is at most XX hours into the past
  - have the client send an explicit requirement for the "producedAt"
    in the ClientHello extension, so that the server can determine
    whether his cached OCSP responses are sufficiently fresh to
    be acceptable to the client -- it would not make much sense
    to send OCSP responses to the client that the client will
    ignore anayway.

Nothing of this requires you to adjust nextUpdate times of
CRLs or OCSP responses.