IETF Logo Mail Archive

Re: [Ntp] Wildcards in NTS certificate checking

"Marco Davids (IETF)" <mdavids@forfun.net> Mon, 18 April 2022 07:11 UTC

Return-Path: <mdavids@forfun.net>
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 CE3863A087B for <ntp@ietfa.amsl.com>; Mon, 18 Apr 2022 00:11:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=forfun.net
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 YvJHVWaMw3_N for <ntp@ietfa.amsl.com>; Mon, 18 Apr 2022 00:11:32 -0700 (PDT)
Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EE7C3A0873 for <ntp@ietf.org>; Mon, 18 Apr 2022 00:11:31 -0700 (PDT)
Received: by mail-ej1-x636.google.com with SMTP id s18so25482136ejr.0 for <ntp@ietf.org>; Mon, 18 Apr 2022 00:11:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=forfun.net; s=google; h=from:message-id:date:mime-version:user-agent:subject :content-language:to:references:organization:in-reply-to :content-transfer-encoding; bh=mStNxchHeO7mdwltGOwRuK0XcHLeubMwmLmMaKiZmqM=; b=WeJObFALfIOeFn4nuL6CYhDeURwuuD77aE14L4LezPHjQcqk+bYt4SknbxKbtF7oaF 9xBG04gnJPGE715BSZVlyKGHHUobOr2VWwAuniZPZuOpc6ljLEbsIk32PzwHGVIs5jUq RDtbuenHYI4VCPVwKFDJQtT+ekayTtBxVZ+Io=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:date:mime-version:user-agent :subject:content-language:to:references:organization:in-reply-to :content-transfer-encoding; bh=mStNxchHeO7mdwltGOwRuK0XcHLeubMwmLmMaKiZmqM=; b=mDzkJzmghobNotpcnvbwNfTPHIwFfBy2TPIp5lub6vToeTfY8QQ3H9yhjIkMDHbaKP bjgpdn+iPy9usuKX80CUfz83Uhi/M12cz9v7NgFRN4rOndmDFiCeM8PZ8Xzth4C4w6jM NunMWEtQSVB6baM6C/yq7iP6VPFkQKB12+wddWY1T2UChOHJQXNPAUzzFzmkbl0MXTEz sG9uTl8D43QG+PyAEPo7dQgi1lbsppsxr303nkRWUWiQAeSZv3pGvbhuJQ/1ohVTYtFw SIMn8oxLGMx7iNTVaUonO1cYhJ1mQcEk4DrxZlRaBzRxjfO07/4e70DRWyvapR8Xn3Tm Tl9g==
X-Gm-Message-State: AOAM531fiPdCZWlBy/4KZJMqZ9CtJ+2Fo1nPcFmuzRH8qaGFSq+rwEsa nLIhRZgE3t04xVCGalmmcehwtgxo8T1Jhd9E
X-Google-Smtp-Source: ABdhPJxuJMLRBTynv7+lg9Kg+sfE5/KxmtlN+/rTieZb+gNgQBPTkBy+02D4VTwMX1S9hMhiKBS7FA==
X-Received: by 2002:a17:906:640a:b0:6e8:643a:7646 with SMTP id d10-20020a170906640a00b006e8643a7646mr8029119ejm.751.1650265888674; Mon, 18 Apr 2022 00:11:28 -0700 (PDT)
Received: from ?IPV6:2a02:a212:2683:1d00:7918:7ca9:971e:b67a? ([2a02:a212:2683:1d00:7918:7ca9:971e:b67a]) by smtp.gmail.com with ESMTPSA id jt24-20020a170906ca1800b006ef606fe5f2sm3059720ejb.61.2022.04.18.00.11.27 for <ntp@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Apr 2022 00:11:28 -0700 (PDT)
From: "Marco Davids (IETF)" <mdavids@forfun.net>
X-Google-Original-From: "Marco Davids (IETF)" <marco.davids@sidn.nl>
Message-ID: <ca2b76cd-76f9-9abf-c385-3b127501a3e1@sidn.nl>
Date: Mon, 18 Apr 2022 09:11:27 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:91.0) Gecko/20100101 Thunderbird/91.8.0
Content-Language: en-GB
To: ntp@ietf.org
References: <20220415203242.60DAF28C1D1@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
Organization: SIDN
In-Reply-To: <20220415203242.60DAF28C1D1@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/klP6m8IDSSI9TDm9jTGStN0SpJQ>
Subject: Re: [Ntp] Wildcards in NTS certificate checking
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 18 Apr 2022 07:11:40 -0000

Op 15-04-22 om 22:32 schreef Hal Murray:

> Where are the NTS servers using wildcards?
> Did something happen recently to trigger this discussion?

I used them on ntppool1.time.nl and ntppool2.time.nl until I found out 
(the hard way) that NTPsec as a client doesn't like them (while Chrony 
does).

Currently I have test server running on nts.time.nl with a wildcard. 
Ironically it is an NTPSec server.

-- 
Marco

v2.23.0 | Report a Bug | By Email