Re: [Acme] Looking for comments on https://github.com/ietf-wg-acme/acme/issues/215

Daniel McCarney <cpu@letsencrypt.org> Mon, 05 December 2016 19:51 UTC

Return-Path: <dmccarney@letsencrypt.org>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37314129531 for <acme@ietfa.amsl.com>; Mon, 5 Dec 2016 11:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=letsencrypt.org
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 X8I1sWG5X5vB for <acme@ietfa.amsl.com>; Mon, 5 Dec 2016 11:51:02 -0800 (PST)
Received: from mail-lf0-x22c.google.com (mail-lf0-x22c.google.com [IPv6:2a00:1450:4010:c07::22c]) (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 5E7481294F3 for <acme@ietf.org>; Mon, 5 Dec 2016 11:51:02 -0800 (PST)
Received: by mail-lf0-x22c.google.com with SMTP id o141so229897722lff.1 for <acme@ietf.org>; Mon, 05 Dec 2016 11:51:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=letsencrypt.org; s=google; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=0mZFhubB0Zr3mJH498wvDVphYHDRAHt0nvR7ONqCoEM=; b=Dl5PNXDzyfyfIJ3IcCe+gxhrjfT7B9teaRopWWfBkQ+Ec1vn4+T9yFYlLHKImNd8kw u1nfwOOPuRd3Oh1BApWfP6PSIJt0tiKy1gVy9yMS6M+Li/mrMxoI+eH3YIjgfZqktHsb Znn+tXFDDYRZdhTHlUrJEjHfBoJcM0Ea8s7d0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=0mZFhubB0Zr3mJH498wvDVphYHDRAHt0nvR7ONqCoEM=; b=d15LfBfALwhgnl21sBVcC74zi91VFsGKBV7pn0kTRoUGFOnE2Q6pWxF7JrTArBXZev XAjD3mTRi4gENBYINFcfNwwueHFlbGtjMcx/ZP3zrY6NPWqIWnbPWrx++cBS48Ax3Zi8 UpAJRU8vZrc+XXZ0Ay3BOvt6EGLOn7ecErcGfmJQWuGHDXG3zSfgv7VnCxhe4yvz4+6+ KBhLDrK+9MAD02TCthsNmJDeInmxEpI2WRi/8H6AYGLXajSaMCeJilMU47sFoVFJOSG1 Qr8OquAZea5u/Fx2WehNDvg6rEa634QM1yKKF43MGwKJKwaH0WgX+72mKHbmnO3ZJPKT OApw==
X-Gm-Message-State: AKaTC00b9SAPHWPaGdOTIiK1G2Z5p+lBvHTYUOfKB0U1f8gfIPJf4Ex5HNHfhXtqeUKoCRaFSUIGcTRZ3PAWFIHX
X-Received: by 10.25.35.6 with SMTP id j6mr21063137lfj.137.1480967460281; Mon, 05 Dec 2016 11:51:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.25.28.206 with HTTP; Mon, 5 Dec 2016 11:50:59 -0800 (PST)
In-Reply-To: <CAL02cgS2k57pM+EgPv3VJzJU-zfFLSmNnSjOnxYf-Pko=OA=kg@mail.gmail.com>
References: <0af93d402273472f9b54603f6aa73e5f@usma1ex-dag1mb1.msg.corp.akamai.com> <CABPsnA=gFpOKSnSd0c4FagQFBWiD8iCrxW8M22m5cO3kY0fPsQ@mail.gmail.com> <CAL02cgS2k57pM+EgPv3VJzJU-zfFLSmNnSjOnxYf-Pko=OA=kg@mail.gmail.com>
From: Daniel McCarney <cpu@letsencrypt.org>
Date: Mon, 05 Dec 2016 14:50:59 -0500
Message-ID: <CAKnbcLh1v3QAc2xejPXdVUSpORrQJ7xYzuYgfrCMrT6=aFiZQA@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
Content-Type: multipart/alternative; boundary="001a113ca7626548f50542ee9b38"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/3Kf6iU9U0TJKobpulBhAuraTrzs>
Cc: "Salz, Rich" <rsalz@akamai.com>, Patrick Figel <patrick@figel.email>, IETF ACME <acme@ietf.org>
Subject: Re: [Acme] Looking for comments on https://github.com/ietf-wg-acme/acme/issues/215
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: cpu@letsencrypt.org
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: Mon, 05 Dec 2016 19:51:06 -0000

Speaking on behalf of Let's Encrypt, we wouldn't be supportive of the change
outlined in #215. We share Patrick's concerns about servers with default
vhosts.

On Sat, Dec 3, 2016 at 5:42 PM, Richard Barnes <rlb@ipv.sx> wrote:

> I find these objections pretty persuasive.  Inclined to WONTFIX.
>
> On Sat, Dec 3, 2016 at 7:35 AM, Patrick Figel <patrick@figel.email> wrote:
>
>> I wrote together some thoughts on this proposal here[1]. In short, I
>> think it's
>> vulnerable to the default vhost attack that caused simpleHTTP to be
>> dropped, and
>> it's not compatible with the "Agreed-Upon Change to Website" method
>> described
>> in the BRs, which would prevent adoption by any publicly-trusted CA.
>>
>> The proposed workaround for this issue[2] would make this a variant of
>> tls-sni,
>> AIUI, which already has these pseudo-hostnames, so I think we're down to
>> "allow
>> other ports" here, and I believe there's consensus against this.
>>
>> Patrick
>>
>> [1]: https://mailarchive.ietf.org/arch/msg/acme/QiXu84RJtURfGVVEY
>> fSpRdtcU5o
>> [2]: https://mailarchive.ietf.org/arch/msg/acme/NFKJ5sqBePGlJglKR
>> wodc5m4ZEo
>>
>> On Sat, Dec 3, 2016 at 3:18 AM, Salz, Rich <rsalz@akamai.com> wrote:
>> > With the couple of recent pull requests, the document editors are about
>> to
>> > close all but on issue, #215.
>> >
>> >
>> >
>> > Does the WG have any feelings on this?  Is it something we need to
>> address
>> > NOW, or can we add a new type of challenge later on if there’s interest?
>> >
>> >
>> >
>> > Please reply on-list by earl next week.
>> >
>> >
>> >
>> > --
>> >
>> > Senior Architect, Akamai Technologies
>> >
>> > Member, OpenSSL Dev Team
>> >
>> > IM: richsalz@jabber.at Twitter: RichSalz
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > Acme mailing list
>> > Acme@ietf.org
>> > https://www.ietf.org/mailman/listinfo/acme
>> >
>>
>> _______________________________________________
>> Acme mailing list
>> Acme@ietf.org
>> https://www.ietf.org/mailman/listinfo/acme
>>
>
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>
>