IETF Logo Mail Archive

Re: [Acme] Server on >= 1024 port

Phillip Hallam-Baker <phill@hallambaker.com> Wed, 02 December 2015 20:00 UTC

Return-Path: <hallam@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 5F9C91B2C6C for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 12:00:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.276
X-Spam-Level:
X-Spam-Status: No, score=-1.276 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=0.001] autolearn=no
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 75LWOxpNUKhN for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 12:00:52 -0800 (PST)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (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 F3A931B2C93 for <acme@ietf.org>; Wed, 2 Dec 2015 12:00:41 -0800 (PST)
Received: by lffu14 with SMTP id u14so65406510lff.1 for <acme@ietf.org>; Wed, 02 Dec 2015 12:00:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=vxKZm7KyVcBJtWISNw2vcC2JG77o4X6kfn63iDtI6J0=; b=l0clzwzUsaq9DgPIwTGcEQmwGexfnztoPOYMv/QoaOSULfiG3JuxoxMW6wfkpOjE9I iHy9RI2sCOTdMZSVimDnYaR8qFDX4sZ9/8/fi5GnURSTtdlf02MPZXLaaqeJr8eI+HtF KN+W7kYqK97q4D7Sa663axvWFgkOBJhEVKeKVId82GAd1u3dm5rIJs77/aqoQCBNCdme wDv/OcUIVb1flMxd3Vry45HxpaEdBkD7N6tPy6r9KYyBcE7LZNskKiYYPkglDjOEfkXx 31BZnGTH9Xi43FzO1BNvvF2M8JXOX+ltdez/ntfECAKKQX5QpGlf4rtOa6CpkAz9lmuH JcwQ==
MIME-Version: 1.0
X-Received: by 10.112.184.45 with SMTP id er13mr3846492lbc.133.1449086440093; Wed, 02 Dec 2015 12:00:40 -0800 (PST)
Sender: hallam@gmail.com
Received: by 10.112.1.227 with HTTP; Wed, 2 Dec 2015 12:00:39 -0800 (PST)
In-Reply-To: <CAO5z66CKVX6y-ejnH3etbMzLwfHdAEgQyc+_d3OOjp4OgXOMWQ@mail.gmail.com>
References: <565589E4.2030107@desy.de> <565EBF56.3070502@desy.de> <D836A378-DA88-4AAF-B1E4-F34A80319DC1@gmail.com> <e9092589f3204a449af8b6f900be1303@usma1ex-dag1mb1.msg.corp.akamai.com> <CAL02cgQPZrx5d1xO-xKEQrV+pZKLkhYW_XDSm=QM8THs__s5qQ@mail.gmail.com> <CANUQDChMFShsjVxOP4XfiMuP3PkKTitr5MM3y3AaNjgyPeaFgA@mail.gmail.com> <23dcf9f85a6a400ca76196e096d22da6@usma1ex-dag1mb1.msg.corp.akamai.com> <CAMm+LwjZc149hfJ3OE-Vi4BgZUdaKqJ1-drKDppMAmqv-JBwxQ@mail.gmail.com> <CAO5z66Daaf2De57AAdZE_Cp_Z-SWVba8PryFnhSn7kDrCKcs3w@mail.gmail.com> <CAMm+Lwh049LvtE_JZ254VqLOiZJEhPcivaaYScrz-u81pzdoww@mail.gmail.com> <CAO5z66CKVX6y-ejnH3etbMzLwfHdAEgQyc+_d3OOjp4OgXOMWQ@mail.gmail.com>
Date: Wed, 02 Dec 2015 15:00:39 -0500
X-Google-Sender-Auth: 355oYjVjPOJJdqWgpjWWUORIYaA
Message-ID: <CAMm+LwiENdVOQp=s+Ar=D0EnPfQUk2XTn2UST2ft+e6aDu8SsA@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Romain Fliedel <romain.fliedel@gmail.com>
Content-Type: multipart/alternative; boundary="001a1133f45082be4d0525efba5c"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/uDwi5JM1m7DTjjYnwvA_Ginrx9I>
Cc: Niklas Keller <me@kelunik.com>, Richard Barnes <rlb@ipv.sx>, "Salz, Rich" <rsalz@akamai.com>, "acme@ietf.org" <acme@ietf.org>, Yoav Nir <ynir.ietf@gmail.com>, Paul Millar <paul.millar@desy.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: Wed, 02 Dec 2015 20:00:54 -0000

On Wed, Dec 2, 2015 at 1:09 PM, Romain Fliedel <romain.fliedel@gmail.com>
wrote:

>
>
> 2015-12-02 18:57 GMT+01:00 Phillip Hallam-Baker <phill@hallambaker.com>:
>
>>
>>
>> On Wed, Dec 2, 2015 at 12:52 PM, Romain Fliedel <romain.fliedel@gmail.com
>> > wrote:
>>
>>> So we might have a record of the form:
>>>>
>>>> example.com  CAA  0 acmedv1 "port=666"
>>>>
>>>>
>>> If you have to modify the dns to use a custom port, why not use the dns
>>> validation method ? (once it's available)
>>>
>>
>> Well there is a slight difference. DNS validation is possibly encumbered
>> for a start.
>>
>> If by DNS validation you mean 'put the response to the challenge in the
>> DNS' then that requires a lot more administrative connection to the DNS
>> than 'put the fingerprint of the validation key in the DNS'
>>
>
> There was a discussion about dns validation that was suggesting using the
> account public key hash as the DNS record value.
> Thus it would be a relatively easy to provision the value correct value.
>
>
Well there is prior art on putting keys in the DNS.

The idea of using the DNS as a channel for a challenge-response mechanism
would make me nervous.

v2.23.0 | Report a Bug | By Email