IETF Logo Mail Archive

Re: [Acme] ACME breaking change: Most GETs become POSTs

Eric Rescorla <ekr@rtfm.com> Fri, 31 August 2018 20:57 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C952130E06 for <acme@ietfa.amsl.com>; Fri, 31 Aug 2018 13:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 okeJ_uO_VSPF for <acme@ietfa.amsl.com>; Fri, 31 Aug 2018 13:57:49 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 34264127B92 for <acme@ietf.org>; Fri, 31 Aug 2018 13:57:49 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id l26-v6so10981770lfc.8 for <acme@ietf.org>; Fri, 31 Aug 2018 13:57:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vTBOJXRAxOXUjIKAOlj3EbA/I5pYFDF/k8pv6zLCFZ4=; b=1qZCnGu+PrH6Fm1C2RfE1SJ4T0Z/gZl1sy66rveX9Tz+3Tj7OhFQ+giFRdCw6spPWD B0ui+jtPUU3vcJRcgM5fonsSV1T88kERS9GgVlM7TFfb5lmyyKJw8kj7QZAGrylhe8j9 /zTkvMDgAKiDnLG5/QkDVFu93zJ1x5+A1O4Pus7/twggIYFGXcXn1ClAGx1nkbxKSyr7 1p4wxggujoYfY202LyA7uxeMj+uyyTf5t1jjXfgkV8dNeKLAxMGmvK8/+qQb/ucDvvOB XVISpEldEF6kYAo6+9/zEPJ3+Fw2GWETWnyii7OwKJJ8kQGDos8RmtJCqsDKtSwX1CRU bVXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vTBOJXRAxOXUjIKAOlj3EbA/I5pYFDF/k8pv6zLCFZ4=; b=Z7y9KbIF6j3cMZmVK0n+p4hgvhdJA0D5hze1NuNCUTbfo3uDl1EQVqur3Wjp8BjcKR E2wfJJJmcGoddUwHiodhxiSyAyZClj7RLMCe3g4nMQqDVo8kx7ltHjn3i/UWep7vkmNg UljZPVJtB3HOn4OzcAvm8SoB3EIe3MKVh1ncQrHJEzIH8ZUKC0sszCGRJVuE9waoidZu BXxc921BX67+dLElSYQhQOqRvAnJsupkdo4jh8y+3+nLgJtiYZDdE4brmBVJ4M2j2JwH 5G6e8sVly1oiaEu7ZHbCFm0t059XgbR/4/ZUtippA7nsJ65TocIn94VY5TprVLKl1Vvc JluQ==
X-Gm-Message-State: APzg51A9Yo6Lxx6aj7J77tpoqqWi8/WXx/VL+sqRgyaXw7ISxCjJzywz K7jz6GGDMPpQzxFHGbjTjR6WqHXLo3wztzvzPswUcA==
X-Google-Smtp-Source: ANB0VdboIT6PVr7PDdlwvfEUdcaJ5FzTURvVLKx6vbjt6G50DXG2q8nNTOL2413hYFD/mLqqtwMwkjulmh0Csnmgjyc=
X-Received: by 2002:a19:e307:: with SMTP id a7-v6mr11290077lfh.125.1535749067407; Fri, 31 Aug 2018 13:57:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ab3:7048:0:0:0:0:0 with HTTP; Fri, 31 Aug 2018 13:57:06 -0700 (PDT)
In-Reply-To: <20180831194333.GE10368@localhost>
References: <c33184f3-4e64-b7ea-babb-d29e2307f1f3@eff.org> <20180831193411.GD10368@localhost> <CAKnbcLjY2NH=FdCkpWGLmPj8iXDqBk4hjF8kfGT18GyOTW4-3g@mail.gmail.com> <20180831194333.GE10368@localhost>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 31 Aug 2018 13:57:06 -0700
Message-ID: <CABcZeBP3T_DDSMLjBhShyjZtka7bvsHRkv521gWtUUtCugrbqg@mail.gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: Daniel McCarney <cpu@letsencrypt.org>, ACME WG <acme@ietf.org>, Jacob Hoffman-Andrews <jsha@eff.org>
Content-Type: multipart/alternative; boundary="000000000000a09b1a0574c1710c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/ZjeFVLpxF-uuCAKnrfEFUWh37bw>
Subject: Re: [Acme] ACME breaking change: Most GETs become POSTs
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.27
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, 31 Aug 2018 20:57:52 -0000

On Fri, Aug 31, 2018 at 12:43 PM, Nico Williams <nico@cryptonector.com>
wrote:

> On Fri, Aug 31, 2018 at 03:37:01PM -0400, Daniel McCarney wrote:
> > > How does using POST address this?
> >
> > Please read the draft. We're talking about POSTs authenticated with JWS
> not
> > vanilla HTTP POSTs.
>
> That really should have been an HTTP authentication method :(
>

Not really, no. First, HTTP is just being used as a transport here. Second,
authentication is by digital signature, and that's not really
well-supported in HTTP. Third, it's way too late now to be having this
discussion.

-Ekr


>
_______________________________________________
> Acme mailing list
> Acme@ietf.org
> https://www.ietf.org/mailman/listinfo/acme
>

v2.23.0 | Report a Bug | By Email