Re: [Ntp] NTP Security (was NTPv5: big picture)

Philip Prindeville <philipp@redfish-solutions.com> Mon, 18 January 2021 20:47 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 B14A93A0A02 for <ntp@ietfa.amsl.com>; Mon, 18 Jan 2021 12:47:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 CZuPAy7hZs8X for <ntp@ietfa.amsl.com>; Mon, 18 Jan 2021 12:47:15 -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 AAEB83A09E8 for <ntp@ietf.org>; Mon, 18 Jan 2021 12:47:15 -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 10IKlDac448799 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 18 Jan 2021 13:47:13 -0700
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
From: Philip Prindeville <philipp@redfish-solutions.com>
In-Reply-To: <acdd42d0-9b58-4b26-0798-55a42bc0b6de@rubidium.se>
Date: Mon, 18 Jan 2021 13:47:12 -0700
Cc: Miroslav Lichvar <mlichvar@redhat.com>, ntp@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <395DA779-0886-4685-B465-E898029C0F78@redfish-solutions.com>
References: <20210118113806.33BBE40605C@ip-64-139-1-69.sjc.megapath.net> <c6fda979-0b3e-99fc-2dc5-25b7cde4c42b@rubidium.se> <20210118162517.GA2410317@localhost> <acdd42d0-9b58-4b26-0798-55a42bc0b6de@rubidium.se>
To: Magnus Danielson <magnus@rubidium.se>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
X-Scanned-By: MIMEDefang 2.84 on 192.168.1.3
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/OkYHzKokmVfBW1i161D7A38CWOU>
Subject: Re: [Ntp] NTP Security (was NTPv5: big picture)
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, 18 Jan 2021 20:47:17 -0000


> On Jan 18, 2021, at 1:17 PM, Magnus Danielson <magnus@rubidium.se> wrote:
> 
>> [...]
> You actually do not trust the time you get initially. You validate it.
> If your DNSSEC is invalid because of time, then the DNSSEC does not
> validate. If your DNSSEC is invalid because false data, the DNSSEC does
> not validate. Then, if and only if DNSSEC validate, only then you get
> time but using the data-validated path, and only then you validate if
> the original time and the validated time match up. If they don't, then
> you do not trust either. If you can spoof the DNSSEC to validate, you
> are toast anyway, if you have put your trust there.
> 
> Now, one *could* argue that the validated time from A can be trusted
> even if the non-validated initial time mismatch. This could be used for
> relaxed rules, but should result in warning.
> 
> If someone feeds you DNS-records that is wrong, DNSSEC should not validate.
> 
> If someone feeds you initial non-validated time that is wrong, that is
> caught later. It may be "good enough" for the DNSSEC to be valid, but we
> do not trust that value any further, it's only used in the boot-strap
> procedure to hand-off to the secured form.
> 
> Cheers,
> Magnus


I think I could live with this.  Rich?  Emmanuel?

-Philip