linux-kernel - RE: [EXT] Re: [PATCH v9 0/2] wifi: mwifiex: add code to support host mlme

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]

Date: Fri, 29 Mar 2024 09:58:32 +0000
From: David Lin <yu-hao.lin@....com>
To: Johannes Berg <johannes@...solutions.net>, Brian Norris
	<briannorris@...omium.org>
CC: Francesco Dolcini <francesco@...cini.it>, "kvalo@...nel.org"
	<kvalo@...nel.org>, "linux-wireless@...r.kernel.org"
	<linux-wireless@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, Pete Hsieh <tsung-hsien.hsieh@....com>,
	rafael.beims <rafael.beims@...adex.com>, Francesco Dolcini
	<francesco.dolcini@...adex.com>
Subject: RE: [EXT] Re: [PATCH v9 0/2] wifi: mwifiex: add code to support host
 mlme

> From: Johannes Berg <johannes@...solutions.net>
> Sent: Monday, March 25, 2024 11:59 PM
> To: Brian Norris <briannorris@...omium.org>
> Cc: David Lin <yu-hao.lin@....com>; Francesco Dolcini
> <francesco@...cini.it>; kvalo@...nel.org; linux-wireless@...r.kernel.org;
> linux-kernel@...r.kernel.org; Pete Hsieh <tsung-hsien.hsieh@....com>;
> rafael.beims <rafael.beims@...adex.com>; Francesco Dolcini
> <francesco.dolcini@...adex.com>
> Subject: Re: [EXT] Re: [PATCH v9 0/2] wifi: mwifiex: add code to support host
> mlme
> 
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, report the message using the 'Report
> this email' button
> 
> 
> On Wed, 2024-03-20 at 14:50 -0700, Brian Norris wrote:
> >
> > AFAICT, mwifiex firmware still isn't allowing "parsing and generation
> > of
> > 802.11 wireless frames" in any general form -- everything I see is
> > still wrapped in custom firmware command protocols. I do see that the
> > AUTH frame looks like it's essentially duplicating the standard mgmt
> > format, and uses the driver's TX path for it, but there isn't a
> > corresponding ASSOC management frame that I can see...
> 
> Fair point, I didn't really look beyond "auth creates auth frames and sends
> them normally like any other frame" ...
> 
> > ...so I really can't tell how much control this firmware *does* give
> > the host regarding arbitrary 802.11 frame management.
> 
> Perhaps indeed FW does require the assoc to be done with that command.
> 

Driver uses assoc command to communicate STA capability to FW. 
FW doesn't need further process Auth so it's converted to 802.11 format and sent directly

> > But that's pretty much business as usual for anybody but the vendor in
> > priorietary firmware land; I can't answer pretty much any question,
> > other than what I can glean from a driver.
> 
> :)
> 
> johannes