IETF Logo Mail Archive

Re: [Acme] Why "HTTP verification"

Peter Bowen <pzbowen@gmail.com> Tue, 02 December 2014 19:15 UTC

Return-Path: <pzbowen@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 898511A6FDD for <acme@ietfa.amsl.com>; Tue, 2 Dec 2014 11:15:49 -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 G8RLJkX_0Xzh for <acme@ietfa.amsl.com>; Tue, 2 Dec 2014 11:15:43 -0800 (PST)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E912C1A6FDE for <acme@ietf.org>; Tue, 2 Dec 2014 11:15:40 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id w10so13770019pde.33 for <acme@ietf.org>; Tue, 02 Dec 2014 11:15:40 -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:content-transfer-encoding; bh=VGkzgDZWiz6ui7XFC1o22VmRWKYVLRQqMmV2MyQX63o=; b=lUWaRrL0kFK77+Mfa51SIx1L9H1mJqbr/kYAJ2naCcZ7A3S2JMoyAQaTA4RD1jpn1k lQC8sk5RaDxEZWYqi/hWSkNXgz7LALnUVyWJjo6X0KoIv6+wdYi+VwWXPBNLBlRvJQN4 8sx679VdaDHwosKiTXwDwwNprqASP19I7v1xgxnyTSVqohbSsrEaIth+81+9KhdC7YXL XYq/Pnly2pjTzJhIHReIu05Rahc8wYUXdST1e4ovjjRbCOnGkvQ1j4hIGL0kBTLpwe5K fAsjaHG0OhAjMWy045j/Brm9kj2QrnO4sHXHX7w/d629ffei15pzVfEFqfwCYpVfBPAD 2ZWg==
MIME-Version: 1.0
X-Received: by 10.70.90.11 with SMTP id bs11mr1759322pdb.16.1417547740203; Tue, 02 Dec 2014 11:15:40 -0800 (PST)
Received: by 10.70.76.10 with HTTP; Tue, 2 Dec 2014 11:15:40 -0800 (PST)
In-Reply-To: <B80ACB30-1A35-440E-B250-AB8C80D1FAF1@vpnc.org>
References: <B80ACB30-1A35-440E-B250-AB8C80D1FAF1@vpnc.org>
Date: Tue, 02 Dec 2014 11:15:40 -0800
Message-ID: <CAK6vND-001PK0gP_3Txoge2hvYiKPuA+trd9zj7PzaooOOMH3A@mail.gmail.com>
From: Peter Bowen <pzbowen@gmail.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/acme/GYfJvemftHvOtiD9jnlTNe63eLA
Cc: acme@ietf.org
Subject: Re: [Acme] Why "HTTP verification"
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: <http://www.ietf.org/mail-archive/web/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: Tue, 02 Dec 2014 19:15:49 -0000

On Tue, Dec 2, 2014 at 10:05 AM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:
> Greetings again. A few people have asked for HTTP-based verification for the certificate request, but I'm not sure that is needed. Are there environments where someone who will be able to stand up a server with a CA-issued cert on HTTPS-over-443 could not stand up such a service with a temporary self-issued cert? If not, what is the value of checking if the person can control the content on port 80?

The primary case where I see a problem is when the site already has a
trusted certificate and wants to use ACME to get a new certificate.
They are unlikely to want to replace their working certificate with a
self-signed certificate.  So the proof would need to happen at the
HTTP layer, not the TLS layer.

Thanks,
Peter

v2.23.0 | Report a Bug | By Email