IETF Logo Mail Archive

Re: [TLS] OCSP must staple

Peter Bowen <pzbowen@gmail.com> Sun, 08 June 2014 16:13 UTC

Return-Path: <pzbowen@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 919E61A0114 for <tls@ietfa.amsl.com>; Sun, 8 Jun 2014 09:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level:
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tt6hMOwR5fPD for <tls@ietfa.amsl.com>; Sun, 8 Jun 2014 09:13:33 -0700 (PDT)
Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC7F91A0089 for <tls@ietf.org>; Sun, 8 Jun 2014 09:13:32 -0700 (PDT)
Received: by mail-ie0-f173.google.com with SMTP id y20so2375922ier.18 for <tls@ietf.org>; Sun, 08 Jun 2014 09:13:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=sTPgLUF11egVk5MBJTfxSpXQF1SSBqs8yPc3GSqQ3+8=; b=0qUMeu+eIxSdOCZNljn5vNPbpHjwQKqPMHw/h8m1kRJJESQqk3jJGxmEnxVDvPLbJL tNT6TA8dSQCsE6agYskhDjIoD9J+PoIFAF74+Ec0DS41iqaCcaN+PZJ2oJJgNsHhT4V/ b6fPt7yEM9cL82J5KXDGu3N8D8Rj2/3rkjlQjPkhsVLmR94fmr6PYx0l318DfN0K44zL SQu3V1/K/fYjDxCa+GGMlaGbwwGw1/JBN1FVcDHwYio9RgY/lsZbv6pBvUmpHSiuVSMY ds1bzez9jUkfKuu1hLM8UKWzss2Ar+FBgWZfbVqBbFu07KtSivrRFGKPNi46qWFxwA/3 ngBQ==
MIME-Version: 1.0
X-Received: by 10.68.231.7 with SMTP id tc7mr21260438pbc.32.1402244012235; Sun, 08 Jun 2014 09:13:32 -0700 (PDT)
Received: by 10.70.56.3 with HTTP; Sun, 8 Jun 2014 09:13:32 -0700 (PDT)
In-Reply-To: <20140608160354.GH27883@mournblade.imrryr.org>
References: <CAFewVt4p4rJ738Yo=XQm6T_jyvG3TnJsSQ5HDZDrqAkyNDa7tg@mail.gmail.com> <20140605173223.GK27883@mournblade.imrryr.org> <20140607164945.GA23329@roeckx.be> <20140607170619.GC27883@mournblade.imrryr.org> <2A0EFB9C05D0164E98F19BB0AF3708C7130F434F7A@USMBX1.msg.corp.akamai.com> <20140607184737.GD27883@mournblade.imrryr.org> <2A0EFB9C05D0164E98F19BB0AF3708C7130F434F7D@USMBX1.msg.corp.akamai.com> <155f01cf82ce$7cfa8360$76ef8a20$@digicert.com> <C877733F-EBCC-4D88-8B99-271914A517B4@gmail.com> <CA+cU71nPXxpk05F+5bthRDXyJKVQwHQGSmT0B3qkCg875B69AQ@mail.gmail.com> <20140608160354.GH27883@mournblade.imrryr.org>
Date: Sun, 08 Jun 2014 09:13:32 -0700
Message-ID: <CAK6vND_iU9vHr9ZK33UCG+v2HTbPh57fe1rV=X3hd9sWH1MwJg@mail.gmail.com>
From: Peter Bowen <pzbowen@gmail.com>
To: "tls@ietf.org" <tls@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/tls/sxxhfmjiVwSmYlKPK3m12lEvGwQ
Subject: Re: [TLS] OCSP must staple
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jun 2014 16:13:34 -0000

On Sun, Jun 8, 2014 at 9:03 AM, Viktor Dukhovni
<viktor1dane@dukhovni.org> wrote:
> On Sun, Jun 08, 2014 at 01:10:47AM -0400, Tom Ritter wrote:
>
>> I don't understand what you mean by the OCSP server rejcting them.
>
> Well, the server was supposed to have stapled, so the OCSP server
> could in principle (knowing the server's certificate requires
> stapling) refuse to provide an unstapled response.

The server is only supposed to staple if the client supports stapling.
Clients that don't support stapling will still make OCSP requests.

v2.23.0 | Report a Bug | By Email