IETF Logo Mail Archive

[Acme] ACME -06: HTTPS authorization

Yaron Sheffer <yaronf.ietf@gmail.com> Tue, 30 May 2017 15:32 UTC

Return-Path: <yaronf.ietf@gmail.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 0C21E1294F8 for <acme@ietfa.amsl.com>; Tue, 30 May 2017 08:32:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.077
X-Spam-Level:
X-Spam-Status: No, score=-0.077 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rzu5dBec9XMi for <acme@ietfa.amsl.com>; Tue, 30 May 2017 08:32:56 -0700 (PDT)
Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 D271A129576 for <acme@ietf.org>; Tue, 30 May 2017 08:32:55 -0700 (PDT)
Received: by mail-wm0-x22a.google.com with SMTP id 7so95109080wmo.1 for <acme@ietf.org>; Tue, 30 May 2017 08:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:message-id:date:user-agent:mime-version :content-language:content-transfer-encoding; bh=yb6U1oH5+BVk2pWAFUEryfOdbFFfTOkQk4muR30CjCY=; b=Y8pyfA5suA4VwMCop1KTUdnxlO8/bdAgIpn98zvnLWM65VLXRzNaGswhrI9wTHxVpe v1zz3uA9ZVShu/zFIAMofNtGyJVkNd7b0fUaEnSn8KbW7NViIkEogxDI0rpEZ5n2D+UT 2hM61ChdcHlYTO9LHCS7s7Jbp2ABg87/7cpJh/ChGNkj+0J/0UAfhcn+9P0OAFA+wRHe xqLjMUNPjudSYvufi+jWRtFfgvuaL+4zcSDvl2RzqxETAKnMnUJYs/G+y5YYjRBZnOZw SpCH13Nme1eYGCidwKIQTXB3svaYXoGNtNtjxDwZjp8E6RXYvkmRGT2qTooH640soVn2 af1Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=yb6U1oH5+BVk2pWAFUEryfOdbFFfTOkQk4muR30CjCY=; b=NI59DdpQLgUt9h3HQfrOqm27lxXnkmyn7JffVfabxU+lqK26NL69sK/jPPZTSPW8Z9 dssqRPCKtS/xF4k0vEMGbOUI/dEgO/CM7BGN0brW5Fq9aLI3919SZLTbMVRkZUvuBFVG 28ZX/O8ChyIBOGk1tZqEDaeszSVBgl8vqYzwW/jYFC5y8m0P8qMHxkcBEyHuy9Oz9C8d Himw5/AtR4CJLhA6UU8xkmPlyPFkgOF/zrUro0QEspE3ZGFyDC+OxqbTrWbyRMbMntAL +m6AMnTi0HSjQC5Z/4ZiSrBqlAoo5R9g4+H1FUyJzGPSK6iJUloIFQBIyB0OF+mT8AFm vIuA==
X-Gm-Message-State: AODbwcBfRjq+OkzlgYyUNe2NPv+Moma5hLswQzSWPXY7EMnaRGk/0N3R RJpDXhT3l5IMmBn9G4I=
X-Received: by 10.28.169.198 with SMTP id s189mr2086291wme.91.1496158374196; Tue, 30 May 2017 08:32:54 -0700 (PDT)
Received: from [10.0.0.1] (bzq-79-178-58-28.red.bezeqint.net. [79.178.58.28]) by smtp.gmail.com with ESMTPSA id c8sm12437857wme.3.2017.05.30.08.32.52 for <acme@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 May 2017 08:32:53 -0700 (PDT)
From: Yaron Sheffer <yaronf.ietf@gmail.com>
To: acme@ietf.org
Message-ID: <7526b3be-65ec-29b6-d657-3e19be06ea6a@gmail.com>
Date: Tue, 30 May 2017 18:32:51 +0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/mKKWN44SO1yepCffKpiIMb5bqEs>
Subject: [Acme] ACME -06: HTTPS authorization
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 30 May 2017 15:32:57 -0000

I'm not sure I understand why the section that describes HTTP validation so specifically forbids using HTTPS. On the other hand, I can think of use cases where I would want *only* HTTPS authorization:

- The server only supports HTTPS, and perhaps port 80 is blocked by a firewall. This situation applies to many REST endpoints.
- I am migrating from a non-ACME to an ACME cert, and so the server has a perfectly valid HTTPS cert. Or migrating from one ACME CA to a different one.
- I would like to ensure (using CAA records) that my CA is not subject to a DNS cache corruption attack - a threat that the ACME Security Considerations specifically mention.

I would suggest that we specify a HTTPS validation that's exactly like http-01, except that it runs over authenticated HTTPS.

Thanks,
    Yaron

v2.23.0 | Report a Bug | By Email