IETF Logo Mail Archive

Re: [certid] Comments on draft-saintandre-tls-server-id-check-04

Matt McCutchen <matt@mattmccutchen.net> Tue, 01 June 2010 19:39 UTC

Return-Path: <matt@mattmccutchen.net>
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 07E483A6A6C for <certid@core3.amsl.com>; Tue, 1 Jun 2010 12:39:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 Lh7S1w7ChQNb for <certid@core3.amsl.com>; Tue, 1 Jun 2010 12:39:33 -0700 (PDT)
Received: from homiemail-a5.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by core3.amsl.com (Postfix) with ESMTP id E67773A6A72 for <certid@ietf.org>; Tue, 1 Jun 2010 12:38:57 -0700 (PDT)
Received: from [192.168.1.41] (pool-74-96-44-249.washdc.east.verizon.net [74.96.44.249]) by homiemail-a5.g.dreamhost.com (Postfix) with ESMTP id 93A09BCDAB for <certid@ietf.org>; Tue, 1 Jun 2010 12:38:45 -0700 (PDT)
From: Matt McCutchen <matt@mattmccutchen.net>
To: certid@ietf.org
In-Reply-To: <465A9C16-F5BF-47B5-A534-25C68CB2988F@jpl.nasa.gov>
References: <4C00FEC0.3080808@edelweb.fr> <201005311518.o4VFIHAw022209@fs4113.wdf.sap.corp> <20100531185813.GA32106@eltex.net> <465A9C16-F5BF-47B5-A534-25C68CB2988F@jpl.nasa.gov>
Content-Type: text/plain; charset="UTF-8"
Date: Tue, 01 Jun 2010 15:38:43 -0400
Message-ID: <1275421123.1918.7.camel@mattlaptop2.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.2
Content-Transfer-Encoding: 7bit
Subject: Re: [certid] Comments on draft-saintandre-tls-server-id-check-04
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, 01 Jun 2010 19:39:37 -0000

On Tue, 2010-06-01 at 11:39 -0700, Henry B. Hotz wrote:
> >> While there have been few implementations checking for multiple
> >> CN= parts, the guideline in rfc-2818 for subjectAltNames seems
> >> to be much clearer, that there can be more than one, and more
> >> than one needs to be checked.
> > 
> > ..and multiple CNs are likely to be an error. I'd better reject this
> > certificate as invalid.
> 
> He says there are "few" implementations that accept what you consider
> an error.  Possibly there are zero, but I hope it's few enough we can
> ignore them.  (Life's complex enough as it is.)

For some test results for implementation support for multiple CNs
(possibly outdated by now), see:

http://wiki.cacert.org/VhostTaskForce#Interoperability_Test

-- 
Matt

v2.8.7 | Report a Bug | By Email