IETF Logo Mail Archive

Re: [Acme] kinds of proof

Randy Bush <randy@psg.com> Tue, 02 December 2014 00:05 UTC

Return-Path: <randy@psg.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 DB1E51A1BE1 for <acme@ietfa.amsl.com>; Mon, 1 Dec 2014 16:05:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.91
X-Spam-Level:
X-Spam-Status: No, score=-6.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, T_RP_MATCHES_RCVD=-0.01] 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 r-mmOXil8bwv for <acme@ietfa.amsl.com>; Mon, 1 Dec 2014 16:05:37 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [198.180.150.18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AEDB1ACD63 for <acme@ietf.org>; Mon, 1 Dec 2014 16:05:29 -0800 (PST)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1Xvay5-0003oz-Vb; Tue, 02 Dec 2014 00:05:26 +0000
Date: Tue, 02 Dec 2014 09:05:24 +0900
Message-ID: <m2tx1ehq63.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <20141129170537.GK285@mournblade.imrryr.org>
References: <CAL02cgTgpjQffow2XuaNuT7BtqYVttXdVUgyqBFbsAbN4g0VzQ@mail.gmail.com> <DEC7A8A8-563D-41B3-94AC-71DC7219D3F8@cisco.com> <m27fyg4yzg.wl%randy@psg.com> <547754C0.9050306@cs.tcd.ie> <20141127211348.GE25114@mournblade.imrryr.org> <54784C61.2080508@cs.tcd.ie> <20141128170917.GC285@mournblade.imrryr.org> <88B49E1D-1601-4B86-8D93-14CF71501DFC@vpnc.org> <20141128213724.GG285@mournblade.imrryr.org> <7261AA75-5912-4514-A393-94F602C941C2@vpnc.org> <20141129170537.GK285@mournblade.imrryr.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
Archived-At: http://mailarchive.ietf.org/arch/msg/acme/pyFzbfkXougpkFP4faPmHCLxVUc
Cc: acme@ietf.org
Subject: Re: [Acme] kinds of proof
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 00:05:41 -0000

>> And it is clear to me that they should be, if we want to see more encryption
>> of traffic. I have no problem with some CAs saying "we'll issue you a cert
>> only if you control port X", but I absolutely want that to be a policy of
>> the CA, not of the enrollment protocol.
> 
> Paul, do you have any examples of CAs that accept any port, or are
> you in part making that up?  Comodo for example, requires control
> of port 80:

or dns

randy

v2.23.0 | Report a Bug | By Email