IETF Logo Mail Archive

Re: [certid] Name constraints and legacy clients

Matt McCutchen <matt@mattmccutchen.net> Mon, 04 October 2010 02:50 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 881B83A6F17 for <certid@core3.amsl.com>; Sun, 3 Oct 2010 19:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599]
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 I8y7mKX1aKdV for <certid@core3.amsl.com>; Sun, 3 Oct 2010 19:50:06 -0700 (PDT)
Received: from homiemail-a61.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by core3.amsl.com (Postfix) with ESMTP id 4448C3A6F12 for <certid@ietf.org>; Sun, 3 Oct 2010 19:50:06 -0700 (PDT)
Received: from homiemail-a61.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a61.g.dreamhost.com (Postfix) with ESMTP id 80075578071; Sun, 3 Oct 2010 19:51:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=mattmccutchen.net; h=subject:from :to:cc:in-reply-to:references:content-type:date:message-id :mime-version:content-transfer-encoding; q=dns; s= mattmccutchen.net; b=M4QjnFYHqbajTbWTNJJqR5dyHjPuIY1lfUpqq53a7tQ TknV2D9JNBsX6P5SKjFu7gVS2GORqgz1xiRNHh+poM4zGmX0afpOrcVpgg+T7aF8 K8gE8QE/fRYMWPXyxqkiQ1OPtqu+son7/ZpyML9eqPexKMUmeldljB2gsPhh0YvU =
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=mattmccutchen.net; h= subject:from:to:cc:in-reply-to:references:content-type:date :message-id:mime-version:content-transfer-encoding; s= mattmccutchen.net; bh=ydSpgX3cxWk7uj86rGQop4D+9gw=; b=ROZCcF4nJQ 3OegMZ7LmdG8M46vEd92zrxd5N2ywMrrR4xsqjbIHRwwkbvwkWx9feuy7AsDqxXR TQNNAgT34wk524Wrmp2Cwp+PSBHH76E6XsSWL98TpBjZArLfVsn/slnNt7Hmd4+P 4DJWnwUGaMUtoCndbloH3HXOHsvonIwzo=
Received: from [129.2.249.209] (ml2.student.umd.edu [129.2.249.209]) (Authenticated sender: matt@mattmccutchen.net) by homiemail-a61.g.dreamhost.com (Postfix) with ESMTPA id EFC2F57806C; Sun, 3 Oct 2010 19:50:59 -0700 (PDT)
From: Matt McCutchen <matt@mattmccutchen.net>
To: Paul Tiemann <paul.tiemann.usenet@gmail.com>
In-Reply-To: <1286160611.14732.125.camel@mattlaptop2.local>
References: <201006301746.o5UHkIsE019133@fs4113.wdf.sap.corp> <4C2B843A.5010206@stpeter.im> <4C305B93.9090001@velox.ch> <201007061435.29786.ludwig.nussel@suse.de> <4C335CE5.1090608@edelweb.fr> <4C3421B3.3070404@velox.ch> <4C3B4F6E.80903@stpeter.im> <4C3DDC18.4020808@bolyard.me> <4C3E979B.4050401@velox.ch> <AANLkTil-6PZ4iAE9SfysI3AuIjam40xbN8DywgLOMwI0@mail.gmail.com> <1286160611.14732.125.camel@mattlaptop2.local>
Content-Type: text/plain; charset="UTF-8"
Date: Sun, 03 Oct 2010 22:50:59 -0400
Message-ID: <1286160659.14732.126.camel@mattlaptop2.local>
Mime-Version: 1.0
X-Mailer: Evolution 2.30.4
Content-Transfer-Encoding: 7bit
Cc: certid@ietf.org
Subject: Re: [certid] Name constraints and legacy clients
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: Mon, 04 Oct 2010 02:50:08 -0000

On Sun, 2010-10-03 at 22:50 -0400, Matt McCutchen wrote:
> Another approach is to have name-constrained intermediate certificates
> include a critical extension that means "name constraints must be
> applied to the CN-ID".  EE certificates under such an intermediate
> certificate will only be accepted by clients that properly enforce the
> name constraints.  An organization could use a name-constrained
> intermediate certificate for servers that don't need to support legacy
> clients and get a certificate directly from a public CA for servers that
> do.  I previously proposed this here:

Sorry.

https://bugzilla.mozilla.org/show_bug.cgi?id=554442

-- 
Matt

v2.8.7 | Report a Bug | By Email