IETF Logo Mail Archive

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

Bryan Livingston <bryanlivingston@gmail.com> Wed, 18 November 2015 20:05 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 4909A1ACD6C for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 12:05:52 -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 909NHKBFV8T7 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 12:05:51 -0800 (PST)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::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 BDA3C1ACD63 for <acme@ietf.org>; Wed, 18 Nov 2015 12:05:50 -0800 (PST)
Received: by lfaz4 with SMTP id z4so34212724lfa.0 for <acme@ietf.org>; Wed, 18 Nov 2015 12:05:48 -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=WjHznLKhhlsHtw3raUQcYOrAfAn20ylOBdka9svRJaM=; b=LS36qJ4TF5pRGXdN43MR7ySYl/uzXv3NiShMA819UMjolRCD+k1ft05WsnVlbnai39 YaIeOii6wSFlscz7JTY1Z2RhEAiphzRpcSc3aEHseQP5a/b7N/q8XqoWLM9wJMf9soFo +UaMBH+wyy+ssKieEuykTa7wDepuDg3REoq2V+dBNC65PFjhL/y9ci4RWK1xwawuKpWN ebF4OZ3la03UYnhnUBdz0TITYz9LLuQTw2G9Z706lUTbC6hwKwpYIebBR5bgu0IfG7tl Po7h+EwwCAlGtNwLhceOdoMD6Y9rM8Y5DHyn6FUcbSe8nVq/GE3IAUdC3DREdZgGaKaB lhxw==
MIME-Version: 1.0
X-Received: by 10.25.210.143 with SMTP id j137mr1636881lfg.86.1447877148861; Wed, 18 Nov 2015 12:05:48 -0800 (PST)
Received: by 10.25.37.19 with HTTP; Wed, 18 Nov 2015 12:05:48 -0800 (PST)
In-Reply-To: <CABkgnnV8=0TVyBU4ugM-R1-izHTx2ugNmOq+MbthQ=qw-r36Hw@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> <CANUQDCizmx=22WwwyVCs55mYYWQ02mYyiGaiC19GG39F9JkViQ@mail.gmail.com> <CABkgnnV8=0TVyBU4ugM-R1-izHTx2ugNmOq+MbthQ=qw-r36Hw@mail.gmail.com>
Date: Wed, 18 Nov 2015 13:05:48 -0700
Message-ID: <CABsBmKNBcpD59DPNLGKBKq+TyhDxFxp1dZfDWfoDnaW3EGm+wA@mail.gmail.com>
From: Bryan Livingston <bryanlivingston@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="001a11408c1a22f1120524d62b6d"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/gy25gV2sV0lvj61zJ7b7UT7aY88>
Cc: Ted Hardie <ted.ietf@gmail.com>, Peter Eckersley <pde@eff.org>, Niklas Keller <me@kelunik.com>, IETF ACME <acme@ietf.org>, Russ Housley <housley@vigilsec.com>, Warren Kumari <warren@kumari.net>
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 20:05:52 -0000

I was thinking that the Authorize Challenge token generated by the server
could have a .txt appended to it. Would the clients just work in that case,
and maybe not need to create a new challenge type?

On Wed, Nov 18, 2015 at 1:00 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 18 November 2015 at 11:03, Niklas Keller <me@kelunik.com> wrote:
> > 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?
>
>
> Presumably, this would be a -02 or -03 version of the protocol and the
> challenge would be identified as "http-02".
>

v2.23.0 | Report a Bug | By Email