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

Peter Gutmann <pgut001@cs.auckland.ac.nz> Wed, 18 March 2015 07:10 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 ED04C1A00C0 for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 00:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 JfLdu_Fponsx for <pkix@ietfa.amsl.com>; Wed, 18 Mar 2015 00:10:15 -0700 (PDT)
Received: from mx2.auckland.ac.nz (mx2.auckland.ac.nz [130.216.125.245]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B199A1A00BD for <pkix@ietf.org>; Wed, 18 Mar 2015 00:10:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=uoa; t=1426662615; x=1458198615; h=from:to:subject:date:message-id: content-transfer-encoding:mime-version; bh=i5zSoCVgLI2WbuCkKmKVpaZ7MqaofI3nsCQ8BbkCxMw=; b=PzlDnzQcCeLOlkx5ZbC9XY5l7dyNauXU2izYmuxojn6G+ScvT2ne2kMB Tzvw+7AaLU7mHqwAkwxTUD/np+KLwddNsqeJ4qcfmsH0wwsyff7vcp78d 70hMVmVRwDo2xzwIV+u3z2qYbpopfrOif0JbmKjTnb+UHzkMTE9r4Qc29 U=;
X-IronPort-AV: E=Sophos;i="5.11,421,1422874800"; d="scan'208";a="314683504"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 130.216.4.125 - Outgoing - Outgoing
Received: from uxchange10-fe3.uoa.auckland.ac.nz ([130.216.4.125]) by mx2-int.auckland.ac.nz with ESMTP/TLS/AES128-SHA; 18 Mar 2015 20:10:12 +1300
Received: from UXCN10-5.UoA.auckland.ac.nz ([169.254.5.82]) by uxchange10-fe3.UoA.auckland.ac.nz ([169.254.143.234]) with mapi id 14.03.0174.001; Wed, 18 Mar 2015 20:10:11 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: IETF PKIX <pkix@ietf.org>
Thread-Topic: [pkix] a question of cert (and OCSP) extension syntax
Thread-Index: AdBhSpLtDh+QMFjMT1+OPRenxqyzHw==
Date: Wed, 18 Mar 2015 07:10:11 +0000
Message-ID: <9A043F3CF02CD34C8E74AC1594475C73AAFB6418@uxcn10-5.UoA.auckland.ac.nz>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/pkix/3BJZzUBrSi5cTPg3LCsXpgajGh0>
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: Wed, 18 Mar 2015 07:10:17 -0000

Melinda Shore <melinda.shore@gmail.com> writes:

>it's what's in the document until someone can either point to some normative
>specification that it violates or can point to something that actually would
>break.

This isn't a case of standards rules-lawyering though (in any case the PKIX
spec is flexible enough that you can stuff anything you want into a
certificate if you interpret things just right, see the famous MPEG-of-cat
quote), it's that this is creating a situation where an *X.509 standards-
compliant certificate* contains data that can't be processed by an *X.509
standards-compliant certificate application*.

Peter.