IETF Logo Mail Archive

Re: [Ntp] Antwort: Why Roughtime?

Ben Laurie <benl@google.com> Tue, 19 December 2023 10:32 UTC

Return-Path: <benl@google.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 90636C151099 for <ntp@ietfa.amsl.com>; Tue, 19 Dec 2023 02:32:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.609
X-Spam-Level:
X-Spam-Status: No, score=-17.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ggLWlCdOhPKV for <ntp@ietfa.amsl.com>; Tue, 19 Dec 2023 02:32:08 -0800 (PST)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4887CC151535 for <ntp@ietf.org>; Tue, 19 Dec 2023 02:32:07 -0800 (PST)
Received: by mail-qt1-x831.google.com with SMTP id d75a77b69052e-425928c24easo272431cf.0 for <ntp@ietf.org>; Tue, 19 Dec 2023 02:32:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20230601; t=1702981926; x=1703586726; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ept7skMpeRtTl/zVOHcdGKogeC0Fwe9UVUqWWeyJBsw=; b=mZUuZoI2QKtnxNQEshj2Piow4reFe359QSbKNE5H0PRSp2yXxFYRebSmV70WSfshkZ HaQK7NxWhVbjV1QevBYgPOq1MFk0grYexRnl2SiQI8M41rD/k8fxcbQyDBpmkD/tcp2B XjOkZ/tGg3J5ebfB7BUiitiwe+npNM4KH+L04sXQi7t/mPI7ccV8CX1n+d4ACMKDNAuD sSyLAvbBh2oosTuwPMUmWPi9pOWiFCd35K9oOv1d1u7eP88UP3/xg3+JsfFve3Pd6ey1 jvQTOwvcy3hrlk1Wi/lDHyIkobYdPuLQGqmxaXjoI1cFQHn2f/536DsjRjT/BAZkQ1U5 sdeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702981926; x=1703586726; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ept7skMpeRtTl/zVOHcdGKogeC0Fwe9UVUqWWeyJBsw=; b=ks7KrmkCld1UYvM6v71fPH/aBJsdKg842Aac68fI/Hyj5cS8YFmgqV7FUJB+F8eu5z p9jbm0eRjYoVaCaUajZ3lUQvqSfhwT7XDOIhFGpUYl712nsdLQMa8h+s9ZUfl5SrQQ3g ZNXHjCiduwkpRRXcaYLcig5HTuw3b4gIKbBhpKKlpTz9EKEZ+3T1cjrX+n8k0FEFcLaV +MB0BilYt2ZwNALys+K/I1G7WmRbGlJnDyFhF+wPGN45G94/d9JU3QmKBNhZpHs9OwDL OhYr4yQrX58u3cL188X+oPgsNYmEH7ZTuxOsh13QlVv5Nb9yYS4wJfnWEtZdd0Y+VaTS j0tw==
X-Gm-Message-State: AOJu0YwAZ7ngfJ6glfCiXrPfIq0KtzjbX8ZV8NgOEngftKOLf6zuvjSd ZxN4vJ+jZG9sIjE16j0mpK60/42e2dXF7BFUMtQgJXVxlw+P
X-Google-Smtp-Source: AGHT+IFn2FQTPFsQLVC1jEeaMa7dDK2NPLJJl6UcmV3s652xvjSCHOpHUAzhON1ZcT8bMmtbnOxg2U1pr5NxyssJYLU=
X-Received: by 2002:a05:622a:1712:b0:425:92a4:b1a8 with SMTP id h18-20020a05622a171200b0042592a4b1a8mr185417qtk.7.1702981925986; Tue, 19 Dec 2023 02:32:05 -0800 (PST)
MIME-Version: 1.0
References: <benl@google.com> <CABrd9SSeQvpSY1JiJn3Nh9FsMFOo1Djk8nR9DoQ1EfRRdOyv7w@mail.gmail.com> <20231218181840.794FD28C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
In-Reply-To: <20231218181840.794FD28C1C3@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
From: Ben Laurie <benl@google.com>
Date: Tue, 19 Dec 2023 10:31:54 +0000
Message-ID: <CABrd9SSPfOcmOyRQNj_o9ctyP+kJPSFuUoKFM2L1bosMediypQ@mail.gmail.com>
To: Hal Murray <halmurray@sonic.net>
Cc: kristof.teichel=40ptb.de@dmarc.ietf.org, ntp@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c23ab3060cda60eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/Egm80QtVkiST04GDJfl-FPyi7bI>
Subject: Re: [Ntp] Antwort: Why Roughtime?
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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: Tue, 19 Dec 2023 10:32:12 -0000

On Mon, 18 Dec 2023 at 18:18, Hal Murray <halmurray@sonic.net> wrote:

>
> Ben Laurie said:
> >  I think you've both missed an important point: if an NTS server gives me
> > incorrect time and I point that out, there's no way for you to know, in
> > general, whether my claim is true or not. With roughtime, I can present
> > evidence.
>
> We can get the evidence with a minor addition to NTS-KE.  We don't need a
> new
> protocol and new set of servers.
>
> What are you going to do with that evidence?  If a server is broken and
> returning bad time to everybody then it will be easy for anybody to
> confirm
> your observation.  Is evidence good for anything other than a legal battle
> when a malicious server is returning bogus time to only your IP address?
>

As Watson has pointed out, we use a similar mechanism in the CA ecosystem
and no legal balles are required. So, yes, evidence is good for things
outside courts.


>
>
>
> --
> These are my opinions.  I hate spam.
>
>
>
>

v2.23.0 | Report a Bug | By Email