Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06)

Jakob Schlyter <jakob@kirei.se> Mon, 21 March 2011 09:58 UTC

Return-Path: <jakob@kirei.se>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 881F63A680C for <keyassure@core3.amsl.com>; Mon, 21 Mar 2011 02:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 ra1LxwPbV8WD for <keyassure@core3.amsl.com>; Mon, 21 Mar 2011 02:58:12 -0700 (PDT)
Received: from spg.kirei.se (spg.kirei.se [91.206.174.9]) by core3.amsl.com (Postfix) with ESMTP id E80BD3A6807 for <keyassure@ietf.org>; Mon, 21 Mar 2011 02:58:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kirei.se; s=spg20100524; h=received:subject:mime-version:content-type:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer; bh=BqE8AcDPfsRcMhqk5fdR4lNYiTa8BALQ+d1awT16BAo=; b=MWt5pxkAS4a3cI3tYLMhKKxC9KFYMEfoAFuUpME3rguwAmb19/GID4RUEdSDCbm48pRyhZnTtG5Uq eWmsvEPhiG6yyaBzf3VNZOtp/y97wl87hXCMZnUoI48b4EZcDV4bWXRSHi0wn6pqH+2dV9Dp2GQQS4 kRpzfJP3LeW+gGII=
Received: from mail.kirei.se (unknown [91.206.174.10]) by spg-relay.kirei.se (Halon Mail Gateway) with ESMTPS; Mon, 21 Mar 2011 10:59:41 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Jakob Schlyter <jakob@kirei.se>
In-Reply-To: <20110321092514.GE9247@anguilla.noreply.org>
Date: Mon, 21 Mar 2011 10:59:39 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AFFDB7BB-8749-4638-AB2D-9ACB617204AC@kirei.se>
References: <4D7BFB41.4000403@vpnc.org> <20110321092514.GE9247@anguilla.noreply.org>
To: Peter Palfrader <peter@palfrader.org>
X-Mailer: Apple Mail (2.1082)
Cc: keyassure@ietf.org, Paul Hoffman <paul.hoffman@vpnc.org>
Subject: Re: [keyassure] CN/SAN matching (was: End entity certificate matching, trust anchors, and protocol-06)
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 09:58:13 -0000

On 21 mar 2011, at 10.25, Peter Palfrader wrote:

> Updating the certificate and its corresponding binding in DNS is not
> dissimilar to updating DNSKEY and DS records: care must be taken to get
> the timing right, so that's a potential source of error.

Update TLSA resource records is very different from update DNSKEY et al. - as long as you take the TTL into consideration, you can update as you wish.

> But even if we do require SNI for TLSA to be useful with virtual
> hosting, that still means a virtual hosting provider has to create a
> certificate for each of the domains they want to serve[2].

Yes, why would that be a problem?

	jakob