Re: [Acme] Server on >= 1024 port

Romain Fliedel <romain.fliedel@gmail.com> Wed, 02 December 2015 18:10 UTC

Return-Path: <romain.fliedel@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 8C10B1ACDE3 for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 10:10:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, SPF_PASS=-0.001, TVD_PH_BODY_ACCOUNTS_PRE=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 Ss7AwIFcFO8I for <acme@ietfa.amsl.com>; Wed, 2 Dec 2015 10:10:19 -0800 (PST)
Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 0E43E1ACDB2 for <acme@ietf.org>; Wed, 2 Dec 2015 10:10:19 -0800 (PST)
Received: by wmec201 with SMTP id c201so266100106wme.0 for <acme@ietf.org>; Wed, 02 Dec 2015 10:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=XpDuZOfkdOB9+DIMtzmzbKbKBIZOabqe21ZieLvmkgs=; b=SOtgpeVihmVIVqsgMjZtinhMedFSRQzKHXTVXABvGkK2MAjr9IAif0tScunrqGV6BJ jFzHSfVhWvhiuvxc5So6Nt8vU9zc2oXOuIYlHWlCwLeZrd70OnvCBRd8pOrnaCZgEZK+ p5yZ8P51tN+tiSJ1kMa6SSCGRUtEabtD+zz8q7Co5Dl9bAstB1+ctH90sJXk6+3X9uJ3 H4gNTTSMhv7GO98WRWGTxkzPHgWxiSvDkdT5lyG3ObmfVDgBYzo6YMUT4aCBlkbChM5q g4BxDN9KQlvf10oNZVHBj2iHDNXq54nufC8VTz0JI2LzkQ4F46Yg/CLytH8Wywqb9qOn SaLw==
X-Received: by 10.194.75.202 with SMTP id e10mr7167717wjw.160.1449079817610; Wed, 02 Dec 2015 10:10:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.154.78 with HTTP; Wed, 2 Dec 2015 10:09:57 -0800 (PST)
In-Reply-To: <CAMm+Lwh049LvtE_JZ254VqLOiZJEhPcivaaYScrz-u81pzdoww@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>
From: Romain Fliedel <romain.fliedel@gmail.com>
Date: Wed, 02 Dec 2015 19:09:57 +0100
Message-ID: <CAO5z66CKVX6y-ejnH3etbMzLwfHdAEgQyc+_d3OOjp4OgXOMWQ@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
Content-Type: multipart/alternative; boundary="047d7bb049c0c7ab9b0525ee2f4e"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/OyKlGzYtyz2vMG4L5DjbPsjtsrk>
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 18:10:22 -0000

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.