Re: [pkix] Amendment to CABF Baseline Requirements

"Erik Andersen" <era@x500.eu> Sat, 08 April 2017 08:20 UTC

Return-Path: <era@x500.eu>
X-Original-To: pkix@ietfa.amsl.com
Delivered-To: pkix@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F2A31293EB for <pkix@ietfa.amsl.com>; Sat, 8 Apr 2017 01:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 wX7pRLQdYymC for <pkix@ietfa.amsl.com>; Sat, 8 Apr 2017 01:20:51 -0700 (PDT)
Received: from mail04.dandomain.dk (mail04.dandomain.dk [194.150.112.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF10E128D2E for <pkix@ietf.org>; Sat, 8 Apr 2017 01:20:50 -0700 (PDT)
Received: from Morten ([62.44.135.123]) by mail04.dandomain.dk (DanDomain Mailserver) with ASMTP id 4201704081020451805 for <pkix@ietf.org>; Sat, 08 Apr 2017 10:20:45 +0200
From: "Erik Andersen" <era@x500.eu>
To: "'IETF PKIX'" <pkix@ietf.org>
References: <906f1c1dde4f44789646197d887da312@EX2.corp.digicert.com> <a24a24b9-542c-a619-3445-47e812f9c46b@nthpermutation.com> <27e9bc684735472bbd6d7f82b5e2823b@EX2.corp.digicert.com> <662C0D5C-EF34-4BD1-B3BC-B7B9A84B4990@vigilsec.com> <CAK6vND9-oxL_acNk21D36UeXHqUM0Rz57cpB_zpCJaTJMPeZ2g@mail.gmail.com> <CA+i=0E5Bh=_b1ZK2T_Y9bj6GivtOJq2Y23i071=wS=jph68tog@mail.gmail.com> <09BE38C5-7B5B-45B0-BC5F-5FCB1164F864@vigilsec.com>
In-Reply-To: <09BE38C5-7B5B-45B0-BC5F-5FCB1164F864@vigilsec.com>
Date: Sat, 8 Apr 2017 10:20:44 +0200
Message-ID: <000001d2b041$050c2310$0f246930$@x500.eu>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01D2B051.C895DD70"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQLbax/O6ZBps7Ft6UeYTkOEFrZPhAFLVKgvAbGqP3EBulwnngL84uHQAprq/+MCV8zYqJ9Eap8g
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/qvJQJ3g0yJqDumYmIUZ_99Byzwc>
Subject: Re: [pkix] Amendment to CABF Baseline Requirements
X-BeenThere: pkix@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 08 Apr 2017 08:20:54 -0000

The change was made in the sixth edition of X.520 (2008). It was primarily driven by Hoyt Kesterson and by some X.500/LDAP vendors. Hoyt was generally against such limitations, as the future is difficult to predict. X.500/LDAP vendors were concerned about interworking between X.500 and LDAP (that does not have upper bounds). You may have noticed that ASN.1 information objects now also contains LDAP specific fields allowing also new attribute types to be usable also in an LDAP environment without the need for additional specifications.

 

I insisted that the upper bounds should be kept in an informative annex to be used by those having a requirement to limit the sizes.

 

I could, if you feel it relevant, try to suggest a Defect Report to X.509 saying that it is strongly recommend to observe the upper bounds specified in X.520. I will also try to get such a statement into any smart grid security standard that references X.509.

 

Erik

Fra: pkix [mailto:pkix-bounces@ietf.org] På vegne af Russ Housley
Sendt: 07 April 2017 22:43
Til: IETF PKIX <pkix@ietf.org>
Emne: Re: [pkix] Amendment to CABF Baseline Requirements

 

The ASN.1 modules that were posted by Erik confirm that the upper bounds have been removed for all of the naming attributes in the SelectedAttributeTypes module.

 

UnboundedDirectoryString ::= CHOICE {

  teletexString    TeletexString(SIZE (1..MAX)),

  printableString  PrintableString(SIZE (1..MAX)),

  bmpString        BMPString(SIZE (1..MAX)),

  universalString  UniversalString(SIZE (1..MAX)),

  uTF8String       UTF8String(SIZE (1..MAX)) }

 

Russ

 

 

On Apr 7, 2017, at 3:15 AM, Erwann Abalea <eabalea@gmail.com <mailto:eabalea@gmail.com> > wrote:

 

Bonjour,

 

2017-04-06 22:39 GMT+02:00 Peter Bowen <pzbowen@gmail.com <mailto:pzbowen@gmail.com> >:

 

On Thu, Apr 6, 2017 at 12:24 PM Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com> > wrote:

The comment in the UpperBounds ASN.1 module (the 8th edition) says:

-- EXPORTS All
-- The types and values defined in this module are exported for use in the other ASN.1
-- modules contained within these Directory Specifications, and for the use of other
-- applications which will use them to access Directory services. Other applications
-- may use them for their own purposes, but this will not constrain extensions and
-- modifications needed to maintain or improve the Directory service.

X.509 is part of the Directory Specifications, so they are not advisory.

It looks like ITU-T increased the length of the organizational unit name in the most recent edition.

RFC 5280 says:

ub-organization-name-length INTEGER ::= 64
ub-organizational-unit-name-length INTEGER ::= 32

The UpperBounds ASN.1 module (the 8th edition) says:

ub-organization-name                       INTEGER ::= 64
ub-organizational-unit-name                INTEGER ::= 64

So, we may already be in a place where implementations conforming to X.509 will produce a certificate that cannot be decoded by an implementation that conforms to RFC 5280.

I wish we gad gotten a heads-up …

 

It is even worse. 7th and 8th (and maybe prior releases) removed the usage of ub- from the schema. The schema itself no longer bounds DirectoryStrings and X.509 explicitly says they are unbounded. 

 

X.520 2005 defines the attributes using the DirectoryString{} parameterized type, while the 2008 edition uses the UnboundedDirectoryString type.

 

RFC5912, which proposes ASN.1 modules for certificates and other related things, still uses the DirectoryString{} variant.

 

-- 

Erwann.