Re: [Ntp] Roughtime server malfeasance proof
James <james.ietf@gmail.com> Wed, 14 December 2022 17:25 UTC
Return-Path: <james.ietf@gmail.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 42BCEC159492 for <ntp@ietfa.amsl.com>; Wed, 14 Dec 2022 09:25:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.095
X-Spam-Level:
X-Spam-Status: No, score=-7.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 z5_DbpN27OSJ for <ntp@ietfa.amsl.com>; Wed, 14 Dec 2022 09:25:49 -0800 (PST)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 85071C14CE41 for <ntp@ietf.org>; Wed, 14 Dec 2022 09:25:49 -0800 (PST)
Received: by mail-ej1-x635.google.com with SMTP id n20so46246602ejh.0 for <ntp@ietf.org>; Wed, 14 Dec 2022 09:25:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=1OqCUmxt/YTUK6POuXdembRyY9IuFnc2GE6FAGP2Cu4=; b=lrLG+prnreWA6nRmo5sA+M8tLbLw2MGK9B1K4fk+YxMQkP/9IRHZ4rZeDBc33FTy0i Nuaw0fXcmBp0ObKMejOc5znToV/2GdJs8M9wmGh4LW9ZFQ7Mk6GB9r6QKViz640bOND7 IrcHnEr/Ns0thJ5Kn946DYzuK6V+hf4WgdOORajDAiRqW4ylyStTRxrt9kWfpMhSy7hl cAgM0xAW2dgjCBjd42jiRo+Fe0T3cmRKNWAD9tYvkfJdU3/CPw9VIT6lCX7yc3m9ciPQ +E2eAa27vZ2dKn+k/frPe3Jt60ut1lY4S2ixW1q7qbBm6xo2rKlH5uQAPDvn15MJ6U6c x0jw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=1OqCUmxt/YTUK6POuXdembRyY9IuFnc2GE6FAGP2Cu4=; b=Sy+akukA4PMOAwlE32jU6RVHE6ih5dv80g0X2w/bCgpE8huyj+vagfKl3pQgdGexn7 ouI+fwnSdk1fF/Ajnn2/s1/JNAVdwhXGgi+H0N6W1naV/RrcUMwmbLBWaih3cv1JBBiX AbbHBZ59vB+1riBYQYF4AyQo/45WElUPb2fKSUcDObxfTRWCfluxJ3GUwSSsDqN59mTX RTx4tTXWnVgX4xOeIh5yeh/eJMOiaP8USBItNiZNx87BE/DZjrwioLuWReX3anhW/o53 bPjSiHbf5tVCJQiUSg++3RutY8C4n2DRzpF9OZ+oFD6aTDv74V7Qudy1hGJmn4k6Y6dX Ii1w==
X-Gm-Message-State: ANoB5plIJjpX30kHSPNSTtZryIFHXUDoWZh2gKXyhvuZorSAPSwQAYAk Kdz+AguaUdWaZfQnxTxpVfN+Bf9YgCc=
X-Google-Smtp-Source: AA0mqf6P29s7b8bTx+S61p0odXaAvdc32H/oUHX10b2oD/NLqZ3NGd3iLP254ijfBFFWr0VPnLyE8g==
X-Received: by 2002:a17:906:2a95:b0:7ad:b14e:d108 with SMTP id l21-20020a1709062a9500b007adb14ed108mr2576211eje.66.1671038747589; Wed, 14 Dec 2022 09:25:47 -0800 (PST)
Received: from smtpclient.apple ([145.15.244.175]) by smtp.gmail.com with ESMTPSA id i13-20020a1709061ccd00b007c11f2a3b3dsm6044380ejh.107.2022.12.14.09.25.47 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Dec 2022 09:25:47 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: James <james.ietf@gmail.com>
In-Reply-To: <CAPz_-SVg6knYNS_DqNSoOReW+OVJreCzEP_avU_8H+5ZUmsquA@mail.gmail.com>
Date: Wed, 14 Dec 2022 18:25:45 +0100
Cc: ntp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EAB9628C-8C93-4948-8B1B-37F7385325ED@gmail.com>
References: <CAPz_-SVg6knYNS_DqNSoOReW+OVJreCzEP_avU_8H+5ZUmsquA@mail.gmail.com>
To: David Venhoek <david@venhoek.nl>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/UXnYF1XjfF7hI2YVgj_7FGoiLWc>
Subject: Re: [Ntp] Roughtime server malfeasance proof
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: Wed, 14 Dec 2022 17:25:51 -0000
My understanding that a single client can't do this, it requires inference from multiple reports of malfeasance. draft-ietf-ntp-roughtime-ecosystem (now expired) left some details and some placeholders for such capabilities. - J > On 13 Dec 2022, at 11:14, David Venhoek <david@venhoek.nl> wrote: > > Dear all, > > The current draft of roughtime seems to suggest that it is possible to > construct a proof of server malfeasance when that occurs. However, in > reading the protocol I cannot find how such proofs can be constructed. > How is that done? > > Kind regards, > David Venhoek > > _______________________________________________ > ntp mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp
- [Ntp] Roughtime server malfeasance proof David Venhoek
- Re: [Ntp] Roughtime server malfeasance proof James