Re: [certid] Please explicitly disallow unvetted info in subject names

Sean Turner <turners@ieca.com> Tue, 08 June 2010 19:43 UTC

Return-Path: <turners@ieca.com>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0EC663A6817 for <certid@core3.amsl.com>; Tue, 8 Jun 2010 12:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.336
X-Spam-Level:
X-Spam-Status: No, score=0.336 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_50=0.001, IP_NOT_FRIENDLY=0.334, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HILbCe-dNCGS for <certid@core3.amsl.com>; Tue, 8 Jun 2010 12:43:02 -0700 (PDT)
Received: from smtp112.biz.mail.sp1.yahoo.com (smtp112.biz.mail.sp1.yahoo.com [69.147.92.225]) by core3.amsl.com (Postfix) with SMTP id 5AD623A6806 for <certid@ietf.org>; Tue, 8 Jun 2010 12:43:02 -0700 (PDT)
Received: (qmail 58429 invoked from network); 8 Jun 2010 19:43:01 -0000
Received: from thunderfish.local (turners@96.231.124.63 with plain) by smtp112.biz.mail.sp1.yahoo.com with SMTP; 08 Jun 2010 12:43:00 -0700 PDT
X-Yahoo-SMTP: ZrP3VLSswBDL75pF8ymZHDSu9B.vcMfDPgLJ
X-YMail-OSG: dlotgZoVM1nGQOMjrCOwPjkxm_iyi6wL1vu.J0XGWtBhSqEAeBWhO8XH6wpttNvt5gXYGAAr8FKIds88GrQWs5UzHREms9ioPIbUw4KCHQYs3GL59X8EW8VhpP0K5IHVXyH6BH7WZeQweloYW8ofBRGvNrl9XLnwo604Zc62i1WzFMCTEyEeim8azdgp4ebmlBgCZZBoWQn3tVsINBILw_Ai3vRIexCqa2R9rE4isj1tn65gYvLt97eG05zGuPqX4cp.MzfFCmGmrz753_w1nKGG8nfE3wtRDLni5xwohFGxaldf3xaYrDY-
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4C0E9D43.7010908@ieca.com>
Date: Tue, 08 Jun 2010 15:42:59 -0400
From: Sean Turner <turners@ieca.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: Paul Hoffman <phoffman@imc.org>
References: <4C0E826B.3050904@bolyard.me> <p06240802c834428416cf@[10.20.30.158]>
In-Reply-To: <p06240802c834428416cf@[10.20.30.158]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: certid@ietf.org
Subject: Re: [certid] Please explicitly disallow unvetted info in subject names
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jun 2010 19:43:03 -0000

Paul Hoffman wrote:
> At 10:48 AM -0700 6/8/10, Nelson B Bolyard wrote:
>> There are a large number of CAs that follow the practice of vetting SOME
>> of the information they put into cert subject names, but not all, and in
>> fact deliberately making no attempt to vet certain attributes at all.
>>
>> Examples known to me include:
>>
>> OU names: typically not vetted at all
>>
>> CNs other than the last (most specific) one, if it is a DNS name.
>>
>> Maybe it's pointless to try, but can we write into this RFC that conforming
>> certs contain NO unvetted attributes in the subject name nor in any Subject
>> Alt Name attributes?
> 
> Their vetting practices are supposed to be listed in their CPSs, so a CA can always say "we do exactly what we say we do" because they know that no one reads (or can read) their CPS.
> 
> Having said that, including this practice as a warning in the document seems like a good idea.

+1

spt