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

Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Thu, 28 January 2021 11:27 UTC

Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 2A1813A0DF6 for <ntp@ietfa.amsl.com>; Thu, 28 Jan 2021 03:27:03 -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 lTsTPCY66N_Z for <ntp@ietfa.amsl.com>; Thu, 28 Jan 2021 03:27:01 -0800 (PST)
Received: from mx1.uni-regensburg.de (mx1.uni-regensburg.de [194.94.157.146]) (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 C4F7B3A0DF0 for <ntp@ietf.org>; Thu, 28 Jan 2021 03:27:00 -0800 (PST)
Received: from mx1.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 83BB2600004F for <ntp@ietf.org>; Thu, 28 Jan 2021 12:26:57 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx1.uni-regensburg.de (Postfix) with ESMTP id 60D4B600004D for <ntp@ietf.org>; Thu, 28 Jan 2021 12:26:57 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Thu, 28 Jan 2021 12:26:57 +0100
Message-Id: <60129F80020000A10003E892@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Thu, 28 Jan 2021 12:26:56 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: "ntp@ietf.org" <ntp@ietf.org>, magnus@rubidium.se
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> <YAX6gJiREb2RE6Gs@roeckx.be> <c5378682-e03f-9e46-24d5-025eb4a57c05@rubidium.se> <20210119094217.GB2430794@localhost> <68c0d807-2290-3c44-d760-35306af20434@rubidium.se> <123A8671-C143-443A-840C-A8960041DADF@redfish-solutions.com> <6e52b053-ed87-fb47-9089-ea321284ef35@rubidium.se> <073B3D3E0200007A6A6A8CFC@gwsmtp.uni-regensburg.de> <B79419B2020000887ED719BE@gwsmtp.uni-regensburg.de> <0F122A330200004A51F0AC03@gwsmtp.uni-regensburg.de> <61C44C9B020000807ED719BE@gwsmtp.uni-regensburg.de> <00535938020000586A6A8CFC@gwsmtp.uni-regensburg.de> <626459A0020000B97ED719BE@gwsmtp.uni-regensburg.de> <AFFAC1180200004BD2E74B8B@gwsmtp.uni-regensburg.de> <98A2DD3B020000927ED719BE@gwsmtp.uni-regensburg.de>
In-Reply-To: <98A2DD3B020000927ED719BE@gwsmtp.uni-regensburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/X7HAB2ijzog9lBRw-2dbSk-h6js>
Subject: [Ntp] Antw: [EXT] Re: 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: Thu, 28 Jan 2021 11:27:03 -0000

>>> Magnus Danielson <magnus@rubidium.se> schrieb am 28.01.2021 um 11:27 in
Nachricht <6e52b053-ed87-fb47-9089-ea321284ef35@rubidium.se>:
> Philip,
> 
> On 2021‑01‑22 03:34, Philip Prindeville wrote:
>>
>>> On Jan 19, 2021, at 5:24 AM, Magnus Danielson <magnus@rubidium.se> wrote:
>>>
>>>> I think the point is that you cannot bootstrap secure time out of
>>>> nothing.
>>> That's a conjecture, yet to be proven.
>>
>> No, that's basic Information Theory.  Lost or non‑existent information
can't 
> be recreated from a void.
>>
>> ...
> Which needs to be properly proven to apply, because we end up shutting
> this WG down if it truely applies.

When "a void" means "maximum entropy" you actually cannot create new
information as creating information increases the entropy.
But fortunately we wouldn't exist in such a state any more, so no reasons to
worry ;-)
Otherwise you are actually not creating information "from a void". Maybe all
out new ideas are just some transformation of information that is already
there...

>>
>>>> You either do full validation using some trusted time source
>>>> (e.g. RTC), or you don't.
>>> RTC is not a trusted time source. 
>>
>> I think I'm more likely to trust that which I can control or verify for 
> myself, than that which I can't.

So you don't trust the RTC initially, but you trust yourself (self-signed
certificate, so to say).

> 
> Which makes it an operational issue, which turns out to fail eventually,
> and when it fails and NTP is your only way to resolve, you do not have
> time and hence you are out of service. That is not leading towards a
> robust solution.
> 
> So, in conclusion, rather than quickly dismiss the notion of being able
> to bootstrap, it needs to be revisited. I through out a proposal to get
> something to test. People did not like that, so now I let others find a
> solution to replace it, and the purpose of my proposal was to provide
> something for people to think and analyze, and find flaws and then fix
> those flaws. What you ended up doing was dismissing the bare thought.
> 
> The lack of interest to solve this means that I see less use and
> therefore less interest in NTPv5.

Out of curiosity: Does anybody know a solution that deduces rough time and
position using a camera pointed at the night sky, using some star almanach?

Regards,
Ulrich

> 
> Cheers,
> Magnus
> 
> _______________________________________________
> ntp mailing list
> ntp@ietf.org 
> https://www.ietf.org/mailman/listinfo/ntp