Re: [Acme] Content-Type and file extensions for HTTP01 challenges
Bryan Livingston <bryanlivingston@gmail.com> Wed, 18 November 2015 15:56 UTC
Return-Path: <bryanlivingston@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 BCA031A9046 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 07:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, HTML_MESSAGE=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 3jY1qjPvGtoz for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 07:56:49 -0800 (PST)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (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 D45E11B36A1 for <acme@ietf.org>; Wed, 18 Nov 2015 07:56:48 -0800 (PST)
Received: by lbblt2 with SMTP id lt2so27108138lbb.3 for <acme@ietf.org>; Wed, 18 Nov 2015 07:56:47 -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=8VrzeVPFkV3nlmnjnbPH5v48uyolbkrVDQGmkzBjL3Y=; b=Mq+djo/f+9+rmiO8FM9hbb1aFdBEn2vNSiZGJjKwdC3swsSpdqF9L2EzW/N84HEYAd k8qEAgtTtgspmzyLlJ1LbNH+4i0BJNLmGJqh4ATMetR72IzgH+UGdhuaK+8wJ+Li0DYZ j7cpAFoEvwYPJE/QTP34/k53NbxmH0R8S3mixAP7uZHpS44CPxnIk5/YKyX6aAICUmV7 YR0jXdVzJfXCDKUodfxhhp8H5sMrIK7IlMvYiJqtI4pxIqUWfMEJApP14WhdTuIgzU1t tb2Yq4TjL42C3UFBNpDVOW6zAbkIuuVeim5ovqDl2rA+bDOm/nQtU8j+UQjDR4CEURTp 8Low==
MIME-Version: 1.0
X-Received: by 10.112.130.195 with SMTP id og3mr909409lbb.69.1447862206844; Wed, 18 Nov 2015 07:56:46 -0800 (PST)
Received: by 10.25.37.19 with HTTP; Wed, 18 Nov 2015 07:56:46 -0800 (PST)
In-Reply-To: <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com>
References: <20151113004436.GB18430@eff.org> <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com> <20151113011259.GC18430@eff.org> <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com>
Date: Wed, 18 Nov 2015 08:56:46 -0700
Message-ID: <CABsBmKM9t3dX0_zq-EwsTOo7HpeMF6meiw9PhBaQLbHOCpGVGg@mail.gmail.com>
From: Bryan Livingston <bryanlivingston@gmail.com>
To: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="047d7b3a83aa85d8850524d2b018"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/b1kwAUS0UzcggJ645u_40RjXQ8Q>
Cc: IETF ACME <acme@ietf.org>
Subject: Re: [Acme] Content-Type and file extensions for HTTP01 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, 18 Nov 2015 15:56:50 -0000
Here's yet another problem reported by a user that would be solved by switching to .txt answer locations. https://github.com/Lone-Coder/letsencrypt-win-simple/issues/7 Typically web servers are already setup to host robots.txt so placing a .txt file on a server should be the least demanding config wise. On Fri, Nov 13, 2015 at 7:56 AM, Russ Housley <housley@vigilsec.com> wrote: > > > I should have added another option, 3b, drop the Content-Type > > restriction but allow file extensions. > > +1 > > This seems like the best balance. > > Russ > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme >
- [Acme] Content-Type and file extensions for HTTP0… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Martin Thomson
- Re: [Acme] Content-Type and file extensions for H… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Russ Housley
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Warren Kumari
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Ted Hardie
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Martin Thomson
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston