linux-kernel - Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZYLKftqKFJ_PMmF3@archie.me>
Date: Wed, 20 Dec 2023 18:05:34 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Hector Martin <marcan@...can.st>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Kalle Valo <kvalo@...nel.org>, Daniel Berlin <dberlin@...rlin.org>,
	Arend van Spriel <arend.vanspriel@...adcom.com>,
	Arend van Spriel <aspriel@...il.com>,
	Franky Lin <franky.lin@...adcom.com>,
	Hante Meuleman <hante.meuleman@...adcom.com>,
	SHA-cyfmac-dev-list@...ineon.com, asahi@...ts.linux.dev,
	brcm80211-dev-list.pdl@...adcom.com, linux-kernel@...r.kernel.org,
	linux-wireless@...r.kernel.org, David Airlie <airlied@...hat.com>,
	Daniel Vetter <daniel@...ll.ch>,
	Dave Stevenson <dave.stevenson@...pberrypi.com>,
	Phil Elwell <phil@...pberrypi.com>,
	Nick Hollinghurst <nick.hollinghurst@...pberrypi.com>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password

On Wed, Dec 20, 2023 at 01:16:20PM +0900, Hector Martin wrote:
> 
> 
> On 2023/12/20 10:44, Linus Torvalds wrote:
> > Put another way: if we effectively don't have a driver maintainer that
> > can test things, and somebody is willing to step up, shouldn't we take
> > that person up on it?
> 
> Personally, I do think the rPi folks themselves should step up for
> *testing* at the very least. I did point them at our downstream WiFi
> branch at one point during a previous discussion and haven't heard back,
> so either they never tested it, or they did and it didn't break
> anything. If they're shipping popular Linux hardware where the WiFi
> chipset vendor has fully and completely checked out of any upstream
> support, they need to either accept that upstream support will likely
> break at some point (because that's just what happens when nobody cares
> about a given piece of hardware, especially with drivers shared across
> others like this one) or they need to proactively step up and take on,
> minimally, an early testing role themselves.

I'm agree that downstream (e.g. rPi) developers should also participating
in upstream kernel development.

Also Cc: rPi folks to solicit their opinions.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)