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

Martin Thomson <martin.thomson@gmail.com> Fri, 13 November 2015 01:05 UTC

Return-Path: <martin.thomson@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 B7A051B3BC6 for <acme@ietfa.amsl.com>; Thu, 12 Nov 2015 17:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 R2qvBK6to8qX for <acme@ietfa.amsl.com>; Thu, 12 Nov 2015 17:05:54 -0800 (PST)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (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 E69DB1B3BC4 for <acme@ietf.org>; Thu, 12 Nov 2015 17:05:53 -0800 (PST)
Received: by igvi2 with SMTP id i2so26896919igv.0 for <acme@ietf.org>; Thu, 12 Nov 2015 17:05:53 -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=EKYDs7u1D1Vd9xCiSSwU3fl9dTV8kfQ5RSBVMT4VJs8=; b=YB3A5PNUlvB45jS9fN89DAaHLRvac7B9f2RkmTB2ffNhjoKktxUXXH5V0RUM4+/ob3 I1lOlM615QaXut7N2Cww7G9FTb2q4V2Gr+pzmFpqcGTODBbN2YBMcIdT6wyJyqq70iUF QWHCm603zgwayvJZrKfaoUTKAzY4Fx4ulBtYh0rpioWhrx0pKe0xFskAlmomojNoiz+n ZiKVUfcbtbyxCydahSlObVGUm2PMtMSgA1rzDjhyOcKhzAE2FHQgXFuPVOP64a0FI+r9 d3uNnL5b/t5qOIiXLWcqsJGbV7tkx7IaXxqIDyVEXK+v28gmnwxA7rFOhxVnpR5AY8zE HyAA==
MIME-Version: 1.0
X-Received: by 10.50.142.8 with SMTP id rs8mr486853igb.77.1447376753371; Thu, 12 Nov 2015 17:05:53 -0800 (PST)
Received: by 10.36.155.139 with HTTP; Thu, 12 Nov 2015 17:05:53 -0800 (PST)
In-Reply-To: <20151113004436.GB18430@eff.org>
References: <20151113004436.GB18430@eff.org>
Date: Thu, 12 Nov 2015 17:05:53 -0800
Message-ID: <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Peter Eckersley <pde@eff.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/RHNyNA_1IijhHkatzArvF4ZUG8I>
Cc: "acme@ietf.org" <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: Fri, 13 Nov 2015 01:05:55 -0000

On 12 November 2015 at 16:44, Peter Eckersley <pde@eff.org> wrote:
> But is 3 the best answer?

Of those presented, I think so.  I know that this isn't a great answer
(it's bad already, so bad must be OK), but being able to drop things
into .well-known opens a raft of other interesting attacks.

More seriously, I think that the other options all have deployment
complications that far outweigh the marginal benefit that extra
checking might provide.