IETF Logo Mail Archive

Re: [pkix] a question of cert (and OCSP) extension syntax

Russ Housley <housley@vigilsec.com> Mon, 30 March 2015 15:22 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FE51AD0B7 for <pkix@ietfa.amsl.com>; Mon, 30 Mar 2015 08:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 S9q22ZqRAUP8 for <pkix@ietfa.amsl.com>; Mon, 30 Mar 2015 08:22:04 -0700 (PDT)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id 185331AD0A2 for <pkix@ietf.org>; Mon, 30 Mar 2015 08:22:04 -0700 (PDT)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 2E6C59A404D; Mon, 30 Mar 2015 11:21:53 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id YL6BWlHnWLEj; Mon, 30 Mar 2015 11:21:52 -0400 (EDT)
Received: from [192.168.2.100] (pool-96-255-133-185.washdc.fios.verizon.net [96.255.133.185]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 8B0049A404A; Mon, 30 Mar 2015 11:21:48 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: multipart/signed; boundary="Apple-Mail-87-597615692"; protocol="application/pkcs7-signature"; micalg="sha1"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <55190678.6080007@comodo.com>
Date: Mon, 30 Mar 2015 11:21:37 -0400
Message-Id: <924332F5-FED1-4A0C-BBD8-146C1AC549B3@vigilsec.com>
References: <9A043F3CF02CD34C8E74AC1594475C73AAFB6418@uxcn10-5.UoA.auckland.ac.nz><C961CE34-4F55-4B11-86D7-1566B701911D@seantek.com><5512C9C7.70202@comodo.com> <55159714.1070902@openca.org> <55190678.6080007@comodo.com>
To: Rob Stradling <rob.stradling@comodo.com>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/Z8c42CTD_-i8rIoJ8RjwgKs6AXU>
Cc: IETF PKIX <pkix@ietf.org>
Subject: Re: [pkix] a question of cert (and OCSP) extension syntax
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 30 Mar 2015 15:22:05 -0000

Rob:

> I think it's only "wrong" and "weird" if you take the view that "if it could conceivably be constructed in ASN.1, then it MUST be constructed in ASN.1".  I don't take that view.

Certificates are ASN.1, and RFC 5280 (and its predecessors) say that extensions are OCTET STRING wrapped ASN.1 structures.  From section 4.2 of RFC 2459:

	Each extension includes an OID and an ASN.1 structure.

Russ

v2.27.8 | Report a Bug | By Email | System Status