IETF Logo Mail Archive

Re: [Acme] Content-Type and file extensions for HTTP01 challenges

Ted Hardie <ted.ietf@gmail.com> Wed, 18 November 2015 18:45 UTC

Return-Path: <ted.ietf@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 5BAFA1A6F12 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 10:45:04 -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 6bnVJZ9vhc2f for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 10:45:02 -0800 (PST)
Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::236]) (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 4940F1A6F0E for <acme@ietf.org>; Wed, 18 Nov 2015 10:45:02 -0800 (PST)
Received: by qgec40 with SMTP id c40so35017035qge.2 for <acme@ietf.org>; Wed, 18 Nov 2015 10:45:01 -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=A38PNLFtO90rYQTREpsYXeovwvxsLl0BDMlo1vd8lbo=; b=nMIm9Jk8pwgDRkWhNV8chy25mrZsdmRcrV2I0eB2vy6nYLgwZBEWxB+u/CCN6XXe2+ 1E5H8tWlUhWJEPyn5xJS1JIZwxtgvMiC9es2GtMzlnWf6BnJmXn9Imc5bJVChuTBxegI jY4DRjqynImIxWHtcFoA2pb2hV0ZfuH5Hanw1BeO4rg8JQ9oaqZ45LIb7HnTfGYGhc0F jvNF+i5hvBfz9gGk2SCV1nJ9Vc8M9sSvoMrKR4YNPRubZ8/RwmjkT2kvAdNEotZqczHs 11Q3wrsinEc8+MRZnvSw41uIdA32KPkbeEXdr+LC12u/COS8x2HlGdDVArnRBxi14tM+ oebA==
MIME-Version: 1.0
X-Received: by 10.140.17.8 with SMTP id 8mr3127612qgc.80.1447872301402; Wed, 18 Nov 2015 10:45:01 -0800 (PST)
Received: by 10.55.115.132 with HTTP; Wed, 18 Nov 2015 10:45:01 -0800 (PST)
In-Reply-To: <20151118180011.GW18430@eff.org>
References: <20151113004436.GB18430@eff.org> <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com> <20151113011259.GC18430@eff.org> <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com> <CABsBmKM9t3dX0_zq-EwsTOo7HpeMF6meiw9PhBaQLbHOCpGVGg@mail.gmail.com> <CAHw9_iJwqqhMb+7+aj6Sszfi6_K9=rREEK3dbpQ6yddrmHSKsg@mail.gmail.com> <CANUQDCgDeaLtaNfeEUQ3D=7EOwjL-Q0i6Q1FKxMTVtfY9d-bow@mail.gmail.com> <20151118180011.GW18430@eff.org>
Date: Wed, 18 Nov 2015 10:45:01 -0800
Message-ID: <CA+9kkMARw2Y86fjFyxoJJU6GJGYmorhJZqCGdns7-CV142v_qA@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: Peter Eckersley <pde@eff.org>
Content-Type: multipart/alternative; boundary="001a11c0ca603491750524d50a79"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/uK8Ty1AOjX-1fEEFAlnCJ588Ws8>
Cc: Warren Kumari <warren@kumari.net>, Russ Housley <housley@vigilsec.com>, IETF ACME <acme@ietf.org>, Niklas Keller <me@kelunik.com>, Bryan Livingston <bryanlivingston@gmail.com>
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 18:45:04 -0000

On Wed, Nov 18, 2015 at 10:00 AM, Peter Eckersley <pde@eff.org> wrote:

> Sounds like we have emerging consensus around this version of 3b.  Does
> anyone know of anything it breaks?
>
> On Wed, Nov 18, 2015 at 05:51:55PM +0100, Niklas Keller wrote:
> > +1 for .txt, there are servers configured to serve only specific file
> > extensions.
> >
> > Regards, Niklas
>
> > _


​So, the original 3b was "3b, drop the Content-Type
restriction but allow file extensions.​" That would allow both text/plain
(with a suffix of .txt if desired) and the original  application/jose+json
(with an appropriate suffix if desired).


Everyone seems to be +1'ing .txt, though, which would be "Switch content
type to text/plain, marked with a suffix as well as a content/type".

Is there anyone arguing for a different content type than text/plain at
this point?

regards,

Ted



> ______________________________________________
> > Acme mailing list
> > Acme@ietf.org
> > https://www.ietf.org/mailman/listinfo/acme
>
>
> --
> Peter Eckersley                            pde@eff.org
> Chief Computer Scientist          Tel  +1 415 436 9333 x131
> Electronic Frontier Foundation    Fax  +1 415 436 9993
>
> _______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>

v2.23.0 | Report a Bug | By Email