Re: [Acme] Content-Type and file extensions for HTTP01 challenges
Russ Housley <housley@vigilsec.com> Fri, 13 November 2015 14:57 UTC
Return-Path: <housley@vigilsec.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 84C7A1A9174 for <acme@ietfa.amsl.com>; Fri, 13 Nov 2015 06:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 AhmXns-EoEDv for <acme@ietfa.amsl.com>; Fri, 13 Nov 2015 06:57:54 -0800 (PST)
Received: from odin.smetech.net (x-bolt-wan.smeinc.net [209.135.219.146]) by ietfa.amsl.com (Postfix) with ESMTP id B0AFC1A916F for <acme@ietf.org>; Fri, 13 Nov 2015 06:57:54 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 4DAD2F2417B for <acme@ietf.org>; Fri, 13 Nov 2015 09:57:44 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id u0iWrIdkAAhm for <acme@ietf.org>; Fri, 13 Nov 2015 09:56:06 -0500 (EST)
Received: from [192.168.2.104] (pool-108-51-128-219.washdc.fios.verizon.net [108.51.128.219]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 4F758F2417F for <acme@ietf.org>; Fri, 13 Nov 2015 09:57:11 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Apple Message framework v1085)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20151113011259.GC18430@eff.org>
Date: Fri, 13 Nov 2015 09:56:52 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com>
References: <20151113004436.GB18430@eff.org> <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com> <20151113011259.GC18430@eff.org>
To: IETF ACME <acme@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/rtcmG09P3HudWUV0YM9WViftOXM>
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: Fri, 13 Nov 2015 14:57:55 -0000
> 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] 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