NetBSD Problem Report #58501

From www@netbsd.org  Sun Jul 28 15:18:26 2024
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits)
	 client-signature RSA-PSS (2048 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 058881A923E
	for <gnats-bugs@gnats.NetBSD.org>; Sun, 28 Jul 2024 15:18:26 +0000 (UTC)
Message-Id: <20240728151824.E0B2C1A9241@mollari.NetBSD.org>
Date: Sun, 28 Jul 2024 15:18:24 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: experimental wg(4) needs known-answer test vectors
X-Send-Pr-Version: www-1.0

>Number:         58501
>Category:       kern
>Synopsis:       experimental wg(4) needs known-answer test vectors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Jul 28 15:20:00 +0000 2024
>Originator:     Taylor R Campbell
>Release:        current, 10
>Organization:
The TestWG Foundation
>Environment:
>Description:
wg(4) needs known-answer test vectors for key derivation, encryption, and decryption, including negative tests to verify forgeries are rejected.

wg(4) also needs self-tests for at least some of these -- ideally all, but the DH computation may be a bit costly to incur at boot when we're not using wg(4).  Maybe it could be done lazily with RUN_ONCE(9).
>How-To-Repeat:
code inspection
>Fix:
These don't appear to be published in the WireGuard whitepaper, so while we can generate them from the code in if_wg.c, we'll have to find some other way to independently generate them to verify.

Home	PR Database Search