IETF Logo Mail Archive

Re: [Acme] Want client-defined callback port

"Salz, Rich" <rsalz@akamai.com> Wed, 22 April 2015 01:24 UTC

Return-Path: <rsalz@akamai.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 018941B301F for <acme@ietfa.amsl.com>; Tue, 21 Apr 2015 18:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level:
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 kEdghG1xcKOL for <acme@ietfa.amsl.com>; Tue, 21 Apr 2015 18:24:14 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (prod-mail-xrelay07.akamai.com [72.246.2.115]) by ietfa.amsl.com (Postfix) with ESMTP id A871F1B301D for <acme@ietf.org>; Tue, 21 Apr 2015 18:24:14 -0700 (PDT)
Received: from prod-mail-xrelay07.akamai.com (localhost.localdomain [127.0.0.1]) by postfix.imss70 (Postfix) with ESMTP id D286E482E5; Wed, 22 Apr 2015 01:24:13 +0000 (GMT)
Received: from prod-mail-relay07.akamai.com (prod-mail-relay07.akamai.com [172.17.121.112]) by prod-mail-xrelay07.akamai.com (Postfix) with ESMTP id C3A9A482E2; Wed, 22 Apr 2015 01:24:13 +0000 (GMT)
Received: from email.msg.corp.akamai.com (ecp.msg.corp.akamai.com [172.27.123.33]) by prod-mail-relay07.akamai.com (Postfix) with ESMTP id BA7BB8003C; Wed, 22 Apr 2015 01:24:13 +0000 (GMT)
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com (172.27.123.102) by usma1ex-dag1mb1.msg.corp.akamai.com (172.27.123.101) with Microsoft SMTP Server (TLS) id 15.0.913.22; Tue, 21 Apr 2015 21:23:49 -0400
Received: from USMA1EX-DAG1MB2.msg.corp.akamai.com ([172.27.123.102]) by usma1ex-dag1mb2.msg.corp.akamai.com ([172.27.123.102]) with mapi id 15.00.0913.011; Tue, 21 Apr 2015 21:23:49 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Bruce Gaya <gaya@apple.com>, Richard Barnes <rlb@ipv.sx>
Thread-Topic: [Acme] Want client-defined callback port
Thread-Index: AQHQeJFWLa11+CsrFEy/G1KlsESTHZ1QpJ+AgAAQ9QCAAA7+AIAAm+aAgAbzyAD//+//8A==
Date: Wed, 22 Apr 2015 01:23:48 +0000
Message-ID: <16985cf1c8c444c48d328fa766ec5ff8@usma1ex-dag1mb2.msg.corp.akamai.com>
References: <352DA5FE-AC6F-49A7-8F9F-70A74889204F@apple.com> <CAK3OfOjey4bk02qC_jj2c0AzZ54qnP=KAJnG=mXnO6A5gZ4m9g@mail.gmail.com> <CAL02cgQ94ijVrCM9SStcodRW+XSG2w5Zwu3+ny8HriDBnxjdtg@mail.gmail.com> <FF21526F-BA8D-4F54-AAE3-047632706668@apple.com> <CAL02cgSDk0TNYusEkXA3onmqF7=kaAWhHjpW8WjbiqxgQMdQwQ@mail.gmail.com> <555F6C74-2416-4893-BDEA-A3C2E55A6D57@apple.com>
In-Reply-To: <555F6C74-2416-4893-BDEA-A3C2E55A6D57@apple.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.56.195]
Content-Type: multipart/alternative; boundary="_000_16985cf1c8c444c48d328fa766ec5ff8usma1exdag1mb2msgcorpak_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/v4WndN4BUrW6TXvbgnmPrZnKXgg>
Cc: Nico Williams <nico@cryptonector.com>, "acme@ietf.org" <acme@ietf.org>
Subject: Re: [Acme] Want client-defined callback 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: <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: Wed, 22 Apr 2015 01:24:17 -0000

I understand that you want it to “just work” (you said that a couple of times :), but other folks have raised security concerns – do you understand or agree with them?

One way forward is to say a client MAY specific a port, where the default is 443. An ACME server MAY reject requests for ports other than 443 if it is in violation of the operating policy.

Does that work?

--
Senior Architect, Akamai Technologies
IM: richsalz@jabber.at Twitter: RichSalz

v2.23.0 | Report a Bug | By Email