[Ntp] security review and NTPv5 modes

Erik Kline <ek.ietf@gmail.com> Sat, 29 July 2023 23:17 UTC

Return-Path: <ek.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 93FF7C14CE4A for <ntp@ietfa.amsl.com>; Sat, 29 Jul 2023 16:17:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 hJuthaYsJyK8 for <ntp@ietfa.amsl.com>; Sat, 29 Jul 2023 16:17:47 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 6B0C9C14CE38 for <ntp@ietf.org>; Sat, 29 Jul 2023 16:17:47 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id af79cd13be357-76ad842d12fso276022485a.3 for <ntp@ietf.org>; Sat, 29 Jul 2023 16:17:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690672666; x=1691277466; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=rgh/VIlHgnj6rB5IqaDROakkOVdl3bMeYkER2Q6cw/s=; b=rxaUjB5b2YdYOwE9LMaTouqUcnmDVKEDTQ/NE2LM1ayI7ERH0pfR+/bZfRa4mElMZD OsUlcsvYdfy9kLo0f6CACJaiEUMTN5zlw3UxTCwflSCeEynL2Csu6FRzQK+0vkx3kJPn itsjlk/v3WMz9wtQn0DTH80dsstDNYFtJBHKXspGyng3CeGwMAVpDqqXMAABRZUKPPAz Iya+jRh+VifFajP6Kw3WmnWI0CeL9Gp0PbuhO/IN/sONRRkeSCo7k0tFjqEwaAOlfLjI PHtQ5YgzvXCKg7WHijpZAvv42+QuHYDZfGE0BKB6+CCRD8iEq+RsIZM1ICevBkUUDvL2 WmyA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690672666; x=1691277466; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=rgh/VIlHgnj6rB5IqaDROakkOVdl3bMeYkER2Q6cw/s=; b=cMSCW5jJSDiDcMI2zjKOMOwvm266VMjAazmFmvRrK9lzkz+5oRb+QmYvfWpq8YdQ2q PWjOGL+GaxNkjP8lxKY6qP09hPuZKDATMe9nwHd5DfdC6/tF1QlwLWrb56rJy2njDa8l Th0dwGHaleibYhGjSVeTfEAt+QmujT2dsmK5KViOAKAEgDitRPQitwkOG8e/Q9Ty/8B2 848aCp1TtXYsvXm/+7oWAFSoR8OQii3WW21rHtfnFnl8TesGA1M+9/f+I0N0KSj3/070 nK9hdAwaOL5ab+r62k0N1Ce3f6le0lCZ6cvpw1MzNIHaJktNN5JYpimnG0MWUsBYUy4n e/zA==
X-Gm-Message-State: ABy/qLbY4sQSS8G+c+X7qANwT+LoLfIUFq/lAfVrTIZwlKGsPVCw653a fggEPYAsc+90jaX46/1cDPQLxHPCGi3i8f6ILmqh6/X5
X-Google-Smtp-Source: APBJJlGiwyiP2XLd+n2rfB69GoZrKHp5X+NJ6EBVQgNFwAToIYa8OtWG70rnHev/d9DR83vnQkTXhon+yj46OWOQhcE=
X-Received: by 2002:a05:620a:294c:b0:767:5984:3ca7 with SMTP id n12-20020a05620a294c00b0076759843ca7mr8513603qkp.40.1690672666130; Sat, 29 Jul 2023 16:17:46 -0700 (PDT)
MIME-Version: 1.0
From: Erik Kline <ek.ietf@gmail.com>
Date: Sat, 29 Jul 2023 16:17:35 -0700
Message-ID: <CAMGpriWoq1Uapy0CPggpi8gRz9zwC5RPZG92dqcyjpOLHMBx7g@mail.gmail.com>
To: NTP WG <ntp@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b23ccc0601a86731"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/mTPnOQc2Uu2R0n9jDpyU29x1Cto>
Subject: [Ntp] security review and NTPv5 modes
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: Sat, 29 Jul 2023 23:17:49 -0000

[putting comments in text since audio was reportedly problematic]

My comment was essentially this:

A *new* protocol without satisfactory security considerations will very
likely be blocked until security concerns have been addressed.

That being said, some strategies I've seen attempted in the past have
included:

    * pointing out that it's not actually "new" and therefore "no worse
than what we have now", and/or

    * adding a very specific applicability statement.

Applicability statements need to clearly outline the circumstances in which
the less secure/insecure thing might be put into operation (like saying
security at some other layer is required, or something).

I don't particularly think these are arguments folks will want to try for
NTPv5.  Just pointing out some kinds of attempted "exemption" text I've
seen.

-ek