IETF Logo Mail Archive

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

Peter Bowen <pzbowen@gmail.com> Tue, 15 December 2015 03:08 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 474841B29F1 for <acme@ietfa.amsl.com>; Mon, 14 Dec 2015 19:08:17 -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 Fz4vmVojMbmo for <acme@ietfa.amsl.com>; Mon, 14 Dec 2015 19:08:15 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (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 AC4041B29F4 for <Acme@ietf.org>; Mon, 14 Dec 2015 19:08:15 -0800 (PST)
Received: by padhk6 with SMTP id hk6so74414576pad.2 for <Acme@ietf.org>; Mon, 14 Dec 2015 19:08:15 -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=Ip86IpkL5v+7Sk1y7TE237D8cOsniPQFpdEsupL720M=; b=phmHgGQ89v/Md2D/8/gEHpkYk5lXfLdaE2uESJf8g2l1DQOG1CUNvNvCtZ2Zjvwz1U WQXJUWgiFfRrwkWlySvJMMcinuFxmMBdMHCRmoHE9gWtiW8igveP79KbXwrwEaJNoPQn uPfviQXjHJXcFLxs4SWX4Xj2ZDYKFOuwbqMm6p2XJJLL+xFpxwhEJODkaskCx0W68yEO eZq1+LdlQvi8SDGlVrJ8gzesAqzVd5IrB+hKFWSfC4/GAuJQiCBJUl3AbrKJLPtsJyii Z76POJ8KpSxcHjdGqUlvSNpfQ6ZwYUBna7eIquRZvp9MUKQywnBvSfAgGBhSwsUTpOgj xUcw==
MIME-Version: 1.0
X-Received: by 10.66.100.163 with SMTP id ez3mr51553019pab.5.1450148895406; Mon, 14 Dec 2015 19:08:15 -0800 (PST)
Received: by 10.66.142.193 with HTTP; Mon, 14 Dec 2015 19:08:15 -0800 (PST)
In-Reply-To: <20151214170035.GA23189@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CAF+SmEpOLoaREymVhi=qOUg2opz1vKzzNp6tGrDTZAjYSKFDkg@mail.gmail.com> <3071e2d95eaf49acac00e91d3626ccfa@usma1ex-dag1mb1.msg.corp.akamai.com> <CAF+SmEo_s8svTgwvBPqqHyhKFKCt5e-3kSpZK2dUAqapzzORiw@mail.gmail.com> <20151214170035.GA23189@LK-Perkele-V2.elisa-laajakaista.fi>
Date: Mon, 14 Dec 2015 19:08:15 -0800
Message-ID: <CAK6vND84uirCOk_LSzMLo5MBDWdmn=DxnZw0KRKjcREQsrkYyw@mail.gmail.com>
From: Peter Bowen <pzbowen@gmail.com>
To: Ilari Liusvaara <ilariliusvaara@welho.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/B6IBceWMMct_RaGHcH1Dw8e6lNc>
Cc: "Salz, Rich" <rsalz@akamai.com>, "Acme@ietf.org" <Acme@ietf.org>, Julian Dropmann <julian@dropmann.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: Tue, 15 Dec 2015 03:08:17 -0000

On Mon, Dec 14, 2015 at 9:00 AM, Ilari Liusvaara
<ilariliusvaara@welho.com> wrote:
> On Mon, Dec 14, 2015 at 05:53:17PM +0100, Julian Dropmann wrote:
>> > >This effectively means, as a domain zone admin, I have to trust every
>> > single service I define, not just to properly deliver this service, but
>> > also not to exploit his ability to obtain signed certificates in my name.
>> >
>> > Yes.
>>
>>
>> And you are perfectly aware, that this was not the case before ACME-enabled
>> CAs existed, and now applies to every single domain admin on this planet,
>> right?
>
> I think there are non-ACME CAs that allow validation mechanism similar to
> the HTTP validation (and where already before ACME ones came really
> around).

Yes, many existing CAs offer validation via HTTP.

Comodo and Thawte/GeoTrust:
https://www.namecheap.com/support/knowledgebase/article.aspx/9637/68/how-can-i-complete-the-domain-control-validation-dcv-for-my-ssl-

GoDaddy:
https://www.godaddy.com/help/verifying-your-domain-ownership-for-ssl-certificate-requests-html-or-dns-7452

SpaceSSL (Certum):
https://spacessl.com/support/ (under Required documents)

ACME didn't invent validation via HTTP.

Thanks,
Peter

v2.23.0 | Report a Bug | By Email