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

"John Levine" <johnl@taugh.com> Thu, 05 April 2018 14:49 UTC

Return-Path: <johnl@iecc.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 00C3D12D963 for <pkix@ietfa.amsl.com>; Thu, 5 Apr 2018 07:49:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.761
X-Spam-Level:
X-Spam-Status: No, score=-1.761 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=JAAjW0Tc; dkim=pass (1536-bit key) header.d=taugh.com header.b=oVpkQlLU
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 c1plgc51Okog for <pkix@ietfa.amsl.com>; Thu, 5 Apr 2018 07:49:48 -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 6B08212D961 for <pkix@ietf.org>; Thu, 5 Apr 2018 07:49:48 -0700 (PDT)
Received: (qmail 66261 invoked from network); 5 Apr 2018 14:49:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=102c8.5ac6378b.k1804; bh=Rxjfjye4cT/NE5fY2ujkmWKEfsxdikTGm8HEOwp52AU=; b=JAAjW0Tcgv8PPQ+zkAwqtLEoEIc9EJHyt0XC5bhIU38Qs4kG0FXLiz8aO1UI/kz0Du9ewGaRlO8wB2/gFaBaTkWxq+Tsr7g/QEntTI4ctszm6W6fV91tqPVlJhpClCeXFXGkiOXsJVl1/LA3uIMMT06o720lmRQT036IOG1Vg1IQsac5mB/C2MTwfDWK0IE0hLJCwYNEwyhMzHZcCEMB/yp9xbhUcNZn7xkjhiMnLWCLsiGBKZ5uu43qOXT5DZJF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=102c8.5ac6378b.k1804; bh=Rxjfjye4cT/NE5fY2ujkmWKEfsxdikTGm8HEOwp52AU=; b=oVpkQlLUEJg/VtOxiIMWkXB74cIhREdxOemCB8BqN4QCR3V5iWOkYxNz6dlMdfUsKxu40/OwU6037VkKwabU3mj4eoiT3N+Eb4X9FCG9n/bEcfFtR6VbUSbx6hRFmzB2bOGmnWZVWPnr7TjEifeFgH8lKqjM0/fTq/w035tEmLzrTDl2VirqLQtALQ2CSqMyxf/2edJcWwXzBo8Z9moQYeRfOdcfUkGTGt98mD+IxTLgK4w6nOQA5ggwI/Y5QthM
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 05 Apr 2018 14:49:46 -0000
Received: by ary.qy (Postfix, from userid 501) id 902F32422295; Thu, 5 Apr 2018 10:49:45 -0400 (EDT)
Date: 5 Apr 2018 10:49:45 -0400
Message-Id: <20180405144946.902F32422295@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: pkix@ietf.org
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/pkix/mRmFgBYucF_kluA3HXjZg0_kBJg>
Subject: [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 14:49:50 -0000

One day I decided to build a content farm, which you can find
at http://www.web.sp.am.  Click on a few of the links and you
will see that it consists of a very large set of similar pages
with names like <a>.<b>.<c>.web.sp.am.

On the theory that even stupid content deserves security, I'd
like to move it to https.  How do I do that?  I got a cert for
*.web.sp.am, but browsers dislike it, saying that the name
in the cert doesn't match the domain name.  I tried to get a
cert for *.*.*.web.sp.am but Let's Encrypt, or at least the
acme.sh client, says multiple wildcards aren't allowed.

Any suggestions?  (Beyond the obvious one to stop wasting my time?)

Tnx,
John