[Ntp] Re: Wrong NTS key exporter context in use for AES-128-GCM-SIV
Miroslav Lichvar <mlichvar@redhat.com> Thu, 19 September 2024 13:36 UTC
Return-Path: <mlichvar@redhat.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 7579EC151520 for <ntp@ietfa.amsl.com>; Thu, 19 Sep 2024 06:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.253
X-Spam-Level:
X-Spam-Status: No, score=-2.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 vQny3r9xGyVo for <ntp@ietfa.amsl.com>; Thu, 19 Sep 2024 06:36:57 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2889C14F6EF for <ntp@ietf.org>; Thu, 19 Sep 2024 06:36:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1726753016; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=xRtQfUYoZUGtifInI1ZRBbxKNiDx7CbpKlUIaik8JwY=; b=XZVFvie05ktbjK3jga0cuLzi/OXsDjwp84ZgJorXkojbDNkZToDSmfeU7Icf1lTwtdTDl4 XxAAzJQfpV8J0orzw7Dz2VnjyEKgNWsDbi6MMY9G5CCZQcWyGF5rchNileFdHZCXpmVBLW DdhZEXF6b8I9d17wnPNtSnnuJvyMmS8=
Received: from mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-611-eF1OTlXLNoyDLTI9GM3AgA-1; Thu, 19 Sep 2024 09:36:52 -0400
X-MC-Unique: eF1OTlXLNoyDLTI9GM3AgA-1
Received: from mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (unknown [10.30.177.4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id A75631955BE5; Thu, 19 Sep 2024 13:36:51 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by mx-prod-int-01.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E8AF530020A2; Thu, 19 Sep 2024 13:36:29 +0000 (UTC)
Date: Thu, 19 Sep 2024 15:36:27 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Hal Murray <halmurray+ietf@sonic.net>
Message-ID: <Zuwo29dACTzqxZdu@localhost>
References: <mlichvar@redhat.com> <Zup4gUwO8kwD3_1N@localhost> <20240918102825.BCFB062003E@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
MIME-Version: 1.0
In-Reply-To: <20240918102825.BCFB062003E@107-137-68-211.lightspeed.sntcca.sbcglobal.net>
X-Scanned-By: MIMEDefang 3.4.1 on 10.30.177.4
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: 3FP6GLLXYKZOQWW7BO4XKMM72B36B6CI
X-Message-ID-Hash: 3FP6GLLXYKZOQWW7BO4XKMM72B36B6CI
X-MailFrom: mlichvar@redhat.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ntp.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: ntp@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Ntp] Re: Wrong NTS key exporter context in use for AES-128-GCM-SIV
List-Id: Network Time Protocol <ntp.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/fEJ-edJZw-mAt1xYzycOzBwJlV0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Owner: <mailto:ntp-owner@ietf.org>
List-Post: <mailto:ntp@ietf.org>
List-Subscribe: <mailto:ntp-join@ietf.org>
List-Unsubscribe: <mailto:ntp-leave@ietf.org>
On Wed, Sep 18, 2024 at 03:28:25AM -0700, Hal Murray wrote: > I can picture a list of things for a client to try against each server. > How big is that list? How many server implementations do we have and how > many configuration options does a server have? > > Does an implementation getting ready for a release have to test all of > their columns and rows in the matrix or is it sufficient to test each > feature with one other implementation? (That's assuming we have already > tested most of the matrix.) I suspect testing every implementation in all possible configurations against every other implementation in all possible configurations will not be practical for too long. We need a set of compliance tests that can be run against each implementation separately. For testing servers there already is this tool [1] that was written in one of the NTS hackathons. It should be extended to cover the GCM issue. For testing clients I have not seen such a thing yet. It could be one of the existing implementations patched with special options to configure the hardcoded things like the AES-128-GCM-SIV vs AES-SIV-CMAC-256 preference and things that can be only changed via build options. [1] https://github.com/mlichvar/ntske-test -- Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… David Venhoek
- [Ntp] Re: Wrong NTS key exporter context in use f… Sanjeev Gupta
- [Ntp] Antwort: Wrong NTS key exporter context in … martin.langer
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Antwort: Wrong NTS key exporter context in … martin.langer
- [Ntp] Re: Wrong NTS key exporter context in use f… Sanjeev Gupta
- [Ntp] Re: Wrong NTS key exporter context in use f… Loganaden Velvindron
- [Ntp] Re: Wrong NTS key exporter context in use f… Daniel Franke
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Daniel Franke
- [Ntp] Wrong NTS key exporter context in use for A… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Hal Murray
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar
- [Ntp] Re: Wrong NTS key exporter context in use f… Martin Mayer
- [Ntp] Re: Wrong NTS key exporter context in use f… Miroslav Lichvar