Received-SPF: pass (google.com: domain of linux-wireless+bounces-3258-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Date: Tue, 6 Feb 2024 22:27:57 +0000
From: Sergei Trofimovich <slyich@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, wireless-regdb@lists.infradead.org,
 Chen-Yu Tsai <wens@kernel.org>, Seth Forshee <sforshee@kernel.org>
Subject: Re: wireless-regdb key change broke crda tests after 37dcea0e6e5
Message-ID: <20240206222757.238a24f8@nz.home>
In-Reply-To: <455bafff0d609eb182ba30a5fbf319888e0e961d.camel@sipsolutions.net>
References: <ZcIXGjzrZrXPCBcp@nz.home>
	<455bafff0d609eb182ba30a5fbf319888e0e961d.camel@sipsolutions.net>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Tue, 06 Feb 2024 12:47:35 +0100
Johannes Berg <johannes@sipsolutions.net> wrote:

> Hi,
> 
> > "wireless-regdb: Update keys and maintainer information".
> > 
> > Both `git` `master` version of `crda` and `wireless-regdb` still fail
> > `crda`'s `make verify`.
> > 
> > Should `crda` key the key update as well?  
> 
> Maybe?
> 
> But perhaps the real question is if you should still be shipping crda?
> It was last needed for kernel 4.15, and even the newest stable kernel
> based on or before it (4.14) is now EOL ...
> 
> After that, we had the regdb loaded like a firmware file including the
> signatures, so the whole crda isn't needed any more.

Great point! `nixpkgs` uses `crda` only as a `hostapd` depend and
looking at modern `hostapd` it does not use it at all. I'll spend some
time removing it downstream. Thank you!

-- 

  Sergei