Re: [Acme] Directory metadata; wildcard support; conditional authz creation

Richard Körber <acme@ml.shredzone.de> Sun, 31 January 2016 19:01 UTC

Return-Path: <acme@ml.shredzone.de>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1C221B2BDA for <acme@ietfa.amsl.com>; Sun, 31 Jan 2016 11:01:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.099
X-Spam-Level: *
X-Spam-Status: No, score=1.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=no
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 gjUSjhOXY1m2 for <acme@ietfa.amsl.com>; Sun, 31 Jan 2016 11:01:23 -0800 (PST)
Received: from arrietty.shredzone.net (arrietty.shredzone.net [213.133.102.195]) (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 04BBD1B2BD8 for <acme@ietf.org>; Sun, 31 Jan 2016 11:01:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=shredzone.net; s=dkim_1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject; bh=iB4UrouBX/Q2xAq9aP1hSxsB/O57zRQp8V0EB4uJHLc=; b=le49lqNIt+1PfdcuE7tV1fmuYK7Ay37D4W7FSOY4ZP2gr0CgtIrKpKS/CUsS9BVXyAlf4b06MqOUE3Ph7X66xdFTZT5/+z3BQw+YHztQYh2dPCCv5Sz+mAls8nHZH70x8MfPaQeDnJDsqjNcxqHdLWT8Y9i5xEZvzl4Szd/foN8=;
Received: from static-87-79-75-184.netcologne.de ([87.79.75.184] helo=ronja.home) by arrietty.shredzone.net with esmtpsa (UNKNOWN:AES128-SHA:128) (Exim 4.72) (envelope-from <acme@ml.shredzone.de>) id 1aPxFP-0004n9-Uq for acme@ietf.org; Sun, 31 Jan 2016 20:01:20 +0100
To: acme@ietf.org
References: <20160131033925.GA29713@andover> <20160130212624.d28caed07b79d3ccb0c24b39@andrewayer.name> <20160131084003.GA26421@andover> <20160131085131.09222b0bd9e64592b75a12f1@andrewayer.name>
From: =?UTF-8?Q?Richard_K=c3=b6rber?= <acme@ml.shredzone.de>
Message-ID: <56AE59FF.9040006@ml.shredzone.de>
Date: Sun, 31 Jan 2016 20:01:19 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <20160131085131.09222b0bd9e64592b75a12f1@andrewayer.name>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/8BgR2thgILhM76AzClJXApRBJiA>
Subject: Re: [Acme] Directory metadata; wildcard support; conditional authz creation
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 31 Jan 2016 19:01:24 -0000

> Perhaps the "hostname" field I proposed could support wildcards.  If the
> server sends the client a challenge with a wildcard in the hostname,
> the client would need to be prepared to respond to the challenge on any
> hostname matching the wildcard.  The CA can choose whether to send
> a challenge for "*.example.com" or just "example.com" when validating a
> wildcard authz for "*.example.com".

I couldn't think of a situation where someone owns and controls a domain, but
would be unable to control any of the subdomains.

So, wouldn't it be sufficient that for a wildcard domain (*.example.com), only
the domain itself (example.com) is challenged?

-- 
Richard Körber