Re: [Acme] Server on >= 1024 port

Yoav Nir <ynir.ietf@gmail.com> Wed, 02 December 2015 14:36 UTC

Return-Path: <ynir.ietf@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 8501D1A90D3 for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 06:36:05 -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 G1a80v_CB_py for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 06:36:04 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 A41781A909D for <acme@ietf.org>; Wed, 2 Dec 2015 06:36:03 -0800 (PST)
Received: by wmww144 with SMTP id w144so59513186wmw.0 for <acme@ietf.org>; Wed, 02 Dec 2015 06:36:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=mEPxJl0Yn7xvRldFqZQGqEO/IkXJ5teyonA3Zk6q60Q=; b=co/en9+fGKJEYW3UwfAAacp9o5oY4kd98i9wrxlehHvYdqrNyq+nHhohSb+ZA0mn2Y gc+YVT1lkQJhAPmpPehQwNsLCyLDVuWZCSlHmQxNiKx0DkPX1YJIWmXKIh8Z35TGBgoy pYlU6CBEyxTstw5uqI+/im1EEMimkiGtqUs8VRVDbEAmrMcwI7aynsBVh6HLelkkx0Au LdfCvXkQHABTNbyHLKE1T3RuU6X0b0N+DpT4rRFCXlgmj8UxKkfzdKC4KWwmEx8j2ssr EdftnmhD+MFfXFF6E2RSp3FIG0iea18ca6k+gQCR/LzpepGftkmv5anXjhLSxLVkbpoi CBpg==
X-Received: by 10.28.19.84 with SMTP id 81mr6753646wmt.26.1449066962273; Wed, 02 Dec 2015 06:36:02 -0800 (PST)
Received: from yoavs-mbp.mshome.net ([176.13.8.115]) by smtp.gmail.com with ESMTPSA id dl8sm3057984wjb.29.2015.12.02.06.36.01 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 02 Dec 2015 06:36:01 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <565EBF56.3070502@desy.de>
Date: Wed, 02 Dec 2015 16:36:00 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D836A378-DA88-4AAF-B1E4-F34A80319DC1@gmail.com>
References: <565589E4.2030107@desy.de> <565EBF56.3070502@desy.de>
To: Paul Millar <paul.millar@desy.de>
X-Mailer: Apple Mail (2.3096.5)
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/wmyWxxEUJBaCueAJ52KZ7l6SInU>
Cc: acme@ietf.org
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: Wed, 02 Dec 2015 14:36:05 -0000

> On 2 Dec 2015, at 11:52 AM, Paul Millar <paul.millar@desy.de> wrote:
> 
> Hi all,
> 
> I'm writing just to summarise this thread and check a consensus has been reached.
> 
> On 25/11/15 11:13, Paul Millar wrote:
>> I was wondering whether people have considered services running on a
>> port other than port 443; in particular, ports greater than 1024.
> 
> The decision is not to support unprivileged ports (>= 1024) because of two factors:
> 
>  1.	ACME wishes to support deployments where there are untrusted
> 	users have (non-root) access to the same machine that
> 	provides a trusted service.
> 
>  2.	There is no supported mechanism for a CA to issue a
> 	certificate that is bound to a specific port.
> 
> Removing either of these points would allow (in principal) ACME to support issuing certificates to services running on unprivileged ports.
> 
> Is that a fair summary?

I think not. I think towards the end the discussion got to a point that we don’t think there is much difference between x>=1024 and x<1024 as long as x!=443. How particular operating systems authorize users to set up servers on different ports is not something we can make sweeping generalizations about. So I don’t think there is consensus to use any port other than 443 for validating certificates for HTTPS.

Yoav