Re: [Ntp] NTPv5 draft

Miroslav Lichvar <mlichvar@redhat.com> Mon, 07 December 2020 10:45 UTC

Return-Path: <mlichvar@redhat.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 E86233A12F1 for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 02:45:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.121
X-Spam-Level:
X-Spam-Status: No, score=-2.121 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
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 N01SJVkkql2B for <ntp@ietfa.amsl.com>; Mon, 7 Dec 2020 02:45:58 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2846A3A136B for <ntp@ietf.org>; Mon, 7 Dec 2020 02:45:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1607337949; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=iieBKIpWgGdLpmy/z9o1xcg//ttazetpE4wtVytQu7E=; b=QYlFoY6R18SQVFZGPKAyeT9CkN/sxRpVmqdTgplLBHQIhb9no1JT4N76xMSZIA99hAmZPe AIZzO0aq3hSiwiuFHyYiO8WdEuYYydgFmJ6L37+tijD3MIXD5hl9sSl4dFzC3cUR/iol5L X5/Jf6MKu77DjXt2VvARnivQvMd00Ew=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-587-1SIEWm-UNmqFuClrAgFf-A-1; Mon, 07 Dec 2020 05:45:48 -0500
X-MC-Unique: 1SIEWm-UNmqFuClrAgFf-A-1
Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 4F406420EA; Mon, 7 Dec 2020 10:45:42 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A1E7E19C45; Mon, 7 Dec 2020 10:45:41 +0000 (UTC)
Date: Mon, 07 Dec 2020 11:45:41 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Dieter Sibold <dsibold.ietf@gmail.com>
Cc: ntp@ietf.org
Message-ID: <20201207104541.GE2352378@localhost>
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>
MIME-Version: 1.0
In-Reply-To: <F62C1325-8409-474C-9650-FA96405D0F4B@gmail.com>
X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/bnn4PVrSh4dMuJ6wiWf3tS8Cg-8>
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 10:46:00 -0000

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.

-- 
Miroslav Lichvar