IETF Logo Mail Archive

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

Niklas Keller <me@kelunik.com> Wed, 18 November 2015 19:03 UTC

Return-Path: <me@kelunik.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 34F7D1A6FE1 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 11:03:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] autolearn=no
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 Fsn4e5oxLz84 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 11:03:32 -0800 (PST)
Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914B01A6FCD for <acme@ietf.org>; Wed, 18 Nov 2015 11:03:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1447873409; l=5836; s=domk; d=kelunik.com; h=Content-Type:Cc:To:From:Subject:Date:References:In-Reply-To: MIME-Version; bh=bhL4g60xFB/IyZEML7tF2uLMFZ8cyVHHubc4Vux2b5Y=; b=lC8uVmryjBSFo2daFmzO3PlJu66ObmlN18AL5Nsii4KMQM97hwrJOwhEX5qj6tn4VuC YJOY6tKjylN9lx6Kdg6BpJ/BDuKHtwOkOwKcP472AB31fEXkuPaGs43gTMpGo+BfzlYQA 2ljTAc3b+D/h2tfOLb08T7NptlwPGAKblv8=
X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLGvomb4bl9EfHtOnM6
X-RZG-CLASS-ID: mo00
Received: from mail-wm0-f50.google.com ([74.125.82.50]) by smtp.strato.de (RZmta 37.14 AUTH) with ESMTPSA id t035bdrAIJ3TyQu (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate) for <acme@ietf.org>; Wed, 18 Nov 2015 20:03:29 +0100 (CET)
Received: by wmdw130 with SMTP id w130so211740167wmd.0 for <acme@ietf.org>; Wed, 18 Nov 2015 11:03:29 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.28.226.11 with SMTP id z11mr6124274wmg.56.1447873409480; Wed, 18 Nov 2015 11:03:29 -0800 (PST)
Received: by 10.194.2.171 with HTTP; Wed, 18 Nov 2015 11:03:29 -0800 (PST)
In-Reply-To: <CA+9kkMARw2Y86fjFyxoJJU6GJGYmorhJZqCGdns7-CV142v_qA@mail.gmail.com>
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> <CA+9kkMARw2Y86fjFyxoJJU6GJGYmorhJZqCGdns7-CV142v_qA@mail.gmail.com>
Date: Wed, 18 Nov 2015 20:03:29 +0100
X-Gmail-Original-Message-ID: <CANUQDCizmx=22WwwyVCs55mYYWQ02mYyiGaiC19GG39F9JkViQ@mail.gmail.com>
Message-ID: <CANUQDCizmx=22WwwyVCs55mYYWQ02mYyiGaiC19GG39F9JkViQ@mail.gmail.com>
From: Niklas Keller <me@kelunik.com>
To: Ted Hardie <ted.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a114b0e024088110524d54c14"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/Lw54qhBnHpqTkdSdlOIrsWs9O_U>
Cc: Warren Kumari <warren@kumari.net>, Peter Eckersley <pde@eff.org>, Russ Housley <housley@vigilsec.com>, IETF ACME <acme@ietf.org>, 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 19:03:33 -0000

How would the transition work? Which URI does the server query then? Both?
Or would the client just send the extension in the challenge answer?

Regards, Niklas

2015-11-18 19:45 GMT+01:00 Ted Hardie <ted.ietf@gmail.com>:

> 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