Re: [Acme] Issuing certificates based on Simple HTTP challenges

Peter Bowen <pzbowen@gmail.com> Wed, 16 December 2015 19:03 UTC

Return-Path: <pzbowen@gmail.com>
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 92D6B1A88D9 for <acme@ietfa.amsl.com>; Wed, 16 Dec 2015 11:03:55 -0800 (PST)
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, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 tjaL88MaSCmr for <acme@ietfa.amsl.com>; Wed, 16 Dec 2015 11:03:53 -0800 (PST)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3D3741A88BA for <acme@ietf.org>; Wed, 16 Dec 2015 11:03:53 -0800 (PST)
Received: by mail-pa0-x22e.google.com with SMTP id wq6so28064421pac.1 for <acme@ietf.org>; Wed, 16 Dec 2015 11:03:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ylINkQNqMpVKZ3REfB/usxbJZqeiupK17TIzD+SUO4=; b=aESTwwG+jMhB3UQJb1jDl4PuzC7WxL2UR67ft9AY68LVKNibiWiYAssUdIUB51ebQF wIGpxbqpuuF4qkmyjAh2YkpBHxBNyiRuEZedOOO+gs0g+ULYVfxqCiV6IR7gnHxsZhoE vWpLKF6eRmLC1HPFXjfh5UK1QsiRYDhEHB3gO77NZHGePLY4/02+PZxEheoZt8P2ALc2 Ry/NR5coX9pxvuzauSSXJz59PLmmJmzIrHIx3v+4+Tp0oD+FD69NcEntWiEY4RwOfEuq T28ZXM4slxX5HGo5qXMBPyS4rYUXqZUW1c3Bt80SVv44rQlIz5+XQNLm9SC7CaMv2l8D jCyQ==
MIME-Version: 1.0
X-Received: by 10.66.221.228 with SMTP id qh4mr24352701pac.68.1450292632876; Wed, 16 Dec 2015 11:03:52 -0800 (PST)
Received: by 10.66.142.193 with HTTP; Wed, 16 Dec 2015 11:03:52 -0800 (PST)
In-Reply-To: <CAF+SmEoJWNgx6=Zp8YC_p+tr2L7fFab3CYhTSyoMJNx+Efzf1g@mail.gmail.com>
References: <CAF+SmEpOLoaREymVhi=qOUg2opz1vKzzNp6tGrDTZAjYSKFDkg@mail.gmail.com> <566F15DC.7090607@wyraz.de> <6B677A87-C6A0-485E-80DF-24960D585F46@coderanger.net> <566F2CB5.90402@wyraz.de> <89774336-0BA6-48FC-821D-1E8F3ED9AC14@coderanger.net> <566F4701.7050308@wyraz.de> <F3DA31B1-B27C-4C63-8ED4-6D27D46FF282@coderanger.net> <C2C239F2-E8A7-499B-BE52-3A48EA92B86D@dropmann.org> <BF7F8411-3E83-4A1F-B3A1-4C37DC8B4618@coderanger.net> <3CDE1749-3143-49EE-BD66-0AE4A8CC4175@dropmann.org> <566FDAB7.2030403@cs.tcd.ie> <56700F68.3040103@wyraz.de> <56701904.2070009@cs.tcd.ie> <56702EFA.1050008@wyraz.de> <13B5E9A8-E9CE-4018-8A9D-7856CBF06B4F@coderanger.net> <CAMm+Lwhvf+nRVV38q1U1DKm1WStV1UJv4+EJ_zvq0G_Tb25S9w@mail.gmail.com> <2761E0B2-8DCC-4150-813F-8CAB756C0392@coderanger.net> <174B082E-2721-41AE-992D-2937DCCB74CB@dropmann.org> <894b0ad1f1c34184bbbc9133702ed474@usma1ex-dag1mb1.msg.corp.akamai.com> <CAMm+Lwgc9Q73BP0CTF=tFQ8a-+-3Oax=nhT5_0wqoHG1_0AnLA@mail.gmail.com> <CAF+SmEoJWNgx6=Zp8YC_p+tr2L7fFab3CYhTSyoMJNx+Efzf1g@mail.gmail.com>
Date: Wed, 16 Dec 2015 11:03:52 -0800
Message-ID: <CAK6vND8D4nfW117WZtrLQ19POi=qsV8ehe9iGttyFwt2ER33Sg@mail.gmail.com>
From: Peter Bowen <pzbowen@gmail.com>
To: Julian Dropmann <julian@dropmann.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/kaYpiVraWko98VjGP0vrSY-Y9O8>
Cc: "Salz, Rich" <rsalz@akamai.com>, Phillip Hallam-Baker <phill@hallambaker.com>, "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] Issuing certificates based on Simple HTTP challenges
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: Wed, 16 Dec 2015 19:03:55 -0000

On Wed, Dec 16, 2015 at 9:35 AM, Julian Dropmann <julian@dropmann.org> wrote:
> Either limit the certificate to be only usable from that origin it has been
> verified from, or somehow get the consent of the domain owner. If not by
> changing DNS config, it might involve some other mechanism.

I think you are somewhat confused.  Certificates are not for full
zones, they only name specific FQDNs.  So a certificate for
"example.com" is not valid for www.example.com or foo.example.com.
Similarly, beta.example.com is not good for example.com or
www.beta.example.com.

RFC 6125 (https://tools.ietf.org/html/rfc6125) covers how certificates
how to do name matching for certificates.  Note that SRVname is the
standard was for things identified via SRV records.

Thanks,
Peter