[TLS] Security of CertificateStatus?
Mike <mike-list@pobox.com> Fri, 16 February 2007 18:07 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HI7UE-0005yc-LN; Fri, 16 Feb 2007 13:07:10 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HI7UD-0005wz-6q for tls@ietf.org; Fri, 16 Feb 2007 13:07:09 -0500
Received: from rune.pobox.com ([208.210.124.79]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HI7UC-0006MJ-0e for tls@ietf.org; Fri, 16 Feb 2007 13:07:09 -0500
Received: from rune (localhost [127.0.0.1]) by rune.pobox.com (Postfix) with ESMTP id 3050AB9C31 for <tls@ietf.org>; Fri, 16 Feb 2007 13:07:29 -0500 (EST)
Received: from [192.168.1.8] (wsip-24-234-114-35.lv.lv.cox.net [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by rune.sasl.smtp.pobox.com (Postfix) with ESMTP id EFFB5B9C30 for <tls@ietf.org>; Fri, 16 Feb 2007 13:07:28 -0500 (EST)
Message-ID: <45D5F218.8010409@pobox.com>
Date: Fri, 16 Feb 2007 10:04:08 -0800
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: tls@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc:
Subject: [TLS] Security of CertificateStatus?
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Errors-To: tls-bounces@lists.ietf.org
I am concerned about the CertificateStatus extension. It only allows for one OCSP response which is the validity of the server's certificate. The problem I see is that most certificate chains have intermediate CA's and their status should also be checked by the client. I'm not too familiar with OCSP yet, so am I missing something? Does the OCSP response contain the validity of an entire certificate chain? Thanks, Mike _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls