Re: [pkix] How do or don't multi-name wildcard certs work?

"John R Levine" <johnl@taugh.com> Thu, 05 April 2018 15:47 UTC

Return-Path: <johnl@taugh.com>
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 4511012D87D for <pkix@ietfa.amsl.com>; Thu, 5 Apr 2018 08:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=rFR6it5c; dkim=pass (1536-bit key) header.d=taugh.com header.b=PDQVlpui
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 mq0udGEdJHCj for <pkix@ietfa.amsl.com>; Thu, 5 Apr 2018 08:47:44 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 3980012D72F for <pkix@ietf.org>; Thu, 5 Apr 2018 08:47:44 -0700 (PDT)
Received: (qmail 85825 invoked from network); 5 Apr 2018 15:47:43 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14f3f.5ac6451f.k1804; bh=YiG8TmObTWPhOktA9HOcQKRDQhYIa+MnoahDyliL2qk=; b=rFR6it5cvNuHtCGqqfqo6d88Qbs7th9rXhDUiq0IyvlUiZV5fRi9h0IO+k8Ck1nSprU/TCzxjaz2yMhGKh41wXNsRJLloGzpI7P7a7fTXHPSEtzG1WfUbx4n3SJlQG5WwkAhXC0c0OovdjM4+RDJ4j1wLKECRWCp0TCGq9FAn4odX1WfFsCJbvWCulaC0LNbsmMA9OjYOP35Lvp/1Olc4mnjHgZHdCcAEGoZhfLa9g3jWC1GtJ7m9Tmx1bUGFotX
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=14f3f.5ac6451f.k1804; bh=YiG8TmObTWPhOktA9HOcQKRDQhYIa+MnoahDyliL2qk=; b=PDQVlpuiTff4wqAssT89sc60ZqExRe13GNUBn381mUPm7WoPNYuRUTGqS1SOqjm8e4sTKQ5fuKffNJbdr22QZShzzfyM3MZy8AB+IOcYEjC5zl9EuVVclNwawNlTbNS9yIqXaAZ/qWqOBo9S1Dv7M1tgT6lmY4UNypyfa1toLOLhU+yo+/USvXwF+1q5uk+LBQi9mizEYqxJ9XwaoneWXbLr9xT02Rps5+nQrIh73aWGH4eWaEWchlmj9m6RDArv
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 05 Apr 2018 15:47:43 -0000
Date: 5 Apr 2018 11:47:42 -0400
Message-ID: <alpine.OSX.2.21.1804051147030.11194@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Ryan Sleevi" <ryan@sleevi.com>
Cc: pkix@ietf.org
In-Reply-To: <CAErg=HHpu0MHHpWy8bCKYFaC9Md98fUrW2ztq-vg9p6R6VgKUg@mail.gmail.com>
References: <20180405144946.902F32422295@ary.qy> <CAErg=HHpu0MHHpWy8bCKYFaC9Md98fUrW2ztq-vg9p6R6VgKUg@mail.gmail.com>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/j4wnFi9J9p_AbaFRSLxdXCbwvKI>
Subject: Re: [pkix] How do or don't multi-name wildcard certs work?
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: Thu, 05 Apr 2018 15:47:46 -0000

> The CA/Browser Forum's Baseline Requirements requires that a wildcard
> certificate is one in which the literal '*.' is prepended to a
> fully-qualified domain (that is, that the wildcard character is the
> left-most label).

So I see now.  I wonder what problem that incompatibility with the DNS was 
supposed to solve.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly