Re: [Ntp] NTPv5 draft

Philip Prindeville <philipp@redfish-solutions.com> Mon, 07 December 2020 18:09 UTC

Return-Path: <philipp@redfish-solutions.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 510183A1641 for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 10:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 inLaETVdf1pf for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 10:09:48 -0800 (PST)
Received: from mail.redfish-solutions.com (mail.redfish-solutions.com [45.33.216.244]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A2353A1640 for <ntp@ietf.org>; Mon, 7 Dec 2020 10:09:48 -0800 (PST)
Received: from [192.168.3.4] ([192.168.3.4]) (authenticated bits=0) by mail.redfish-solutions.com (8.16.1/8.16.1) with ESMTPSA id 0B7I9j9f117342 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 7 Dec 2020 11:09:46 -0700
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.20.0.2.21\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <20201207104541.GE2352378@localhost>
Date: Mon, 07 Dec 2020 11:09:45 -0700
Cc: Dieter Sibold <dsibold.ietf@gmail.com>, ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AF8032D3-DAC2-4F35-9727-32275ADC784C@redfish-solutions.com>
References: <20201111161947.GG1559650@localhost> <AA848C67-CFB7-43FC-B190-FD3911360373@gmail.com> <20201201081203.GB1900232@localhost> <2B8C7410-DFA7-4A87-A33E-F50FFA96D0F9@gmail.com> <20201201100305.GK1900232@localhost> <F62C1325-8409-474C-9650-FA96405D0F4B@gmail.com> <20201207104541.GE2352378@localhost>
To: Miroslav Lichvar <mlichvar@redhat.com>
X-Mailer: Apple Mail (2.3654.20.0.2.21)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/39pzh8cN0f5kG7NaAN7JVdGdjPc>
Subject: Re: [Ntp] NTPv5 draft
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Dec 2020 18:09:49 -0000


> On Dec 7, 2020, at 3:45 AM, Miroslav Lichvar <mlichvar@redhat.com> wrote:
> 
> On Fri, Dec 04, 2020 at 05:58:16PM +0100, Dieter Sibold wrote:
>>> Ok, so if the draft said something like "NTP clients SHOULD use
>>> authentication", would that work for you? Ultimately, it would be up
>>> to the client's default configuration whether authentication is
>>> enabled or not.
>>> 
>> 
>> No. From my point of view this is not explicit. I would prefer that the
>> basic protocol incorporates security. That would allow to use security
>> without thinking about which approach needs to be applied to accomplish
>> that. For the experts there might be additional option like the pre-shared
>> key approach to acknowledge very specific circumstances. But the normal NTP
>> user should be able to use a secured NTPv5 like using a https protected
>> website.
> 
> Ok, I see your point, but I don't think it's a good idea. NTPv5 was
> supposed to fix other issues. I don't remember anyone complaining that
> NTPv4 can be used without authentication. That's a feature, not a bug.
> It's up to the implementations and their default configurations to
> enable authentication.
> 
> Web browsers still default to HTTP and how long does HTTPS exist?
> 
> NTS just become a thing. Forcing people to NTS by removing
> unauthenticated NTP from NTPv5 won't work.
> 

HTTP isn’t by definition used to control infrastructure, and when it is used that way, HTTPS is usually mandated.

V4 goes back to 2010, but as I remember it was in use as protocol for a while before the implementation was written up and standardized.

And there were fewer known exploits then than now.

-Philip