Re: [Acme] Server on >= 1024 port

Stephen Farrell <stephen.farrell@cs.tcd.ie> Thu, 26 November 2015 11:35 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
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 D76EA1A03A3 for <acme@ietfa.amsl.com>; Thu, 26 Nov 2015 03:35:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.886
X-Spam-Level:
X-Spam-Status: No, score=-4.886 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.585, 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 wLDG8SeflT44 for <acme@ietfa.amsl.com>; Thu, 26 Nov 2015 03:35:46 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C8D61A039F for <acme@ietf.org>; Thu, 26 Nov 2015 03:35:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id C9C13BE3E; Thu, 26 Nov 2015 11:35:44 +0000 (GMT)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PmTXrVdJ9HrZ; Thu, 26 Nov 2015 11:35:44 +0000 (GMT)
Received: from [134.226.62.192] (cswireless62-192.scss.tcd.ie [134.226.62.192]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id F3287BE39; Thu, 26 Nov 2015 11:35:43 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1448537744; bh=dDN3JtQGDP8R0taDUvVsY5+Ai/xu9KJFh94ZQId8y2E=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=SFIMgISv6AcE45uq90+krV/spTHuDmnt9kKGK6QFE8v4AJDEqNTqkV9K/7t4BxwCU 0FY0wUxBqdybaNveFPbatfy2pDQIuxR2WNlptcJ/UFDHTRMmTEYd/2ouZoKwj0cA7L r5swsKId8tIMwki6c1cbGiPjlJPzZpmfwRRiLqWg=
To: Rob Stradling <rob.stradling@comodo.com>, Yoav Nir <ynir.ietf@gmail.com>
References: <565589E4.2030107@desy.de> <5655EC72.7060300@moparisthebest.com> <CABcZeBOJ6O+P3U1EJoRkKaHaJVVBtLiQwpRp5aNOa+fX-noPjQ@mail.gmail.com> <5655EFCF.9090403@moparisthebest.com> <5655FC50.7000508@zinks.de> <m2lh9lko2j.wl%randy@psg.com> <5D0426D4-683C-46DF-B44C-B3F048536236@gmail.com> <5656EDD2.8030601@comodo.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <5656EE8F.1080108@cs.tcd.ie>
Date: Thu, 26 Nov 2015 11:35:43 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <5656EDD2.8030601@comodo.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/T5yG--EE6dLBNZxZzoVjgniRcpM>
Cc: Randy Bush <randy@psg.com>, acme WG <acme@ietf.org>, Roland Zink <roland@zinks.de>
Subject: Re: [Acme] Server on >= 1024 port
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: Thu, 26 Nov 2015 11:35:50 -0000


On 26/11/15 11:32, Rob Stradling wrote:
> On 26/11/15 11:20, Yoav Nir wrote:
> <snip>
>> Another thing is that I don’t get why some CAs have the web *client*
>> authentication EKU thrown in there.
> 
> Because a sufficiently large number of customers asked for it.  :-)
> 
> AIUI the use case is server-to-server comms, where server A acts as a
> TLS client and server B requires TLS client auth.  Server A also acts as
> a TLS server and its operator doesn't want to have to manage 2 different
> certs.

Yep. I also want that. Not needed everywhere but it's good to have.

S.

>