From: Brian Norris <briannorris@chromium.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Kalle Valo <kvalo@kernel.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Francesco Dolcini <francesco.dolcini@toradex.com>
Subject: Re: [PATCH v2 2/2] wifi: mwifiex: add support for WPA-PSK-SHA256
Date: Thu, 18 Jul 2024 15:55:18 -0700 [thread overview]
Message-ID: <ZpmdVq2CkxRcLxvO@google.com> (raw)
In-Reply-To: <20240717-mwifiex-wpa-psk-sha256-v2-2-eb53d5082b62@pengutronix.de>
Hi Sascha,
On Wed, Jul 17, 2024 at 10:30:08AM +0200, Sascha Hauer wrote:
> This adds support for the WPA-PSK AKM suite with SHA256 as hashing
> method (WPA-PSK-SHA256). Tested with a wpa_supplicant provided AP
> using key_mgmt=WPA-PSK-SHA256.
>
> Reviewed-by: Francesco Dolcini <francesco.dolcini@toradex.com>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> drivers/net/wireless/marvell/mwifiex/fw.h | 1 +
> drivers/net/wireless/marvell/mwifiex/uap_cmd.c | 3 +++
> 2 files changed, 4 insertions(+)
>
> diff --git a/drivers/net/wireless/marvell/mwifiex/fw.h b/drivers/net/wireless/marvell/mwifiex/fw.h
> index 3adc447b715f6..1c76754b616ff 100644
> --- a/drivers/net/wireless/marvell/mwifiex/fw.h
> +++ b/drivers/net/wireless/marvell/mwifiex/fw.h
> @@ -415,6 +415,7 @@ enum MWIFIEX_802_11_PRIVACY_FILTER {
> #define KEY_MGMT_NONE 0x04
> #define KEY_MGMT_PSK 0x02
> #define KEY_MGMT_EAP 0x01
> +#define KEY_MGMT_PSK_SHA256 0x100
> #define CIPHER_TKIP 0x04
> #define CIPHER_AES_CCMP 0x08
> #define VALID_CIPHER_BITMAP 0x0c
> diff --git a/drivers/net/wireless/marvell/mwifiex/uap_cmd.c b/drivers/net/wireless/marvell/mwifiex/uap_cmd.c
> index 7f822660fd955..c055fdc7114ba 100644
> --- a/drivers/net/wireless/marvell/mwifiex/uap_cmd.c
> +++ b/drivers/net/wireless/marvell/mwifiex/uap_cmd.c
> @@ -60,6 +60,9 @@ int mwifiex_set_secure_params(struct mwifiex_private *priv,
> case WLAN_AKM_SUITE_PSK:
> bss_config->key_mgmt = KEY_MGMT_PSK;
> break;
> + case WLAN_AKM_SUITE_PSK_SHA256:
> + bss_config->key_mgmt = KEY_MGMT_PSK_SHA256;
> + break;
I feel like this relates to previous questions you've had [1], and while
I think the answer at the time made sense to me (basically, EAP and PSK
are mutually exclusive), it makes less sense to me here that PSK-SHA256
is mutually exclusive with PSK. And in particular, IIUC, this means that
the ordering in a wpa_supplicant.conf line like
key_mgmt=WPA-PSK WPA-PSK-SHA256
matters -- only the latter will actually be in use.
Is that intended? Is this really a single-value field, and not a
multiple-option bitfield?
Or if these are really mutually exclusive, then maybe we're on the wrong
track here:
https://patchwork.kernel.org/project/linux-wireless/patch/20240530130156.1651174-1-s.hauer@pengutronix.de/
wifi: mwifiex: increase max_num_akm_suites
In any case, something feels off here, because the nl80211 API doesn't
say anything about the ordering of AKM suites being relevant.
Brian
> default:
> break;
> }
>
> --
> 2.39.2
>
[1] Subject: Re: [EXT] Re: [PATCH v10 2/2] wifi: mwifiex: add host mlme for AP mode
https://lore.kernel.org/all/Zmvjw3aG9j8kW0Ld@pengutronix.de/
https://lore.kernel.org/all/PA4PR04MB9638B7F0F4E49F79057C15FBD1CD2@PA4PR04MB9638.eurprd04.prod.outlook.com/
next prev parent reply other threads:[~2024-07-18 22:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 8:30 [PATCH v2 0/2] mwifiex: add support for WPA-PSK-SHA256 Sascha Hauer
2024-07-17 8:30 ` [PATCH v2 1/2] wifi: mwifiex: simplify WPA flags setting Sascha Hauer
2024-07-17 8:40 ` Francesco Dolcini
2024-07-18 22:40 ` Brian Norris
2024-07-17 8:30 ` [PATCH v2 2/2] wifi: mwifiex: add support for WPA-PSK-SHA256 Sascha Hauer
2024-07-18 22:55 ` Brian Norris [this message]
2024-07-19 6:04 ` Sascha Hauer
2024-07-19 19:05 ` Brian Norris
2024-07-22 7:48 ` Sascha Hauer
2024-07-22 8:46 ` [EXT] " David Lin
2024-07-22 19:30 ` Brian Norris
2024-07-23 7:04 ` Sascha Hauer
2024-07-22 10:57 ` Francesco Dolcini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZpmdVq2CkxRcLxvO@google.com \
--to=briannorris@chromium.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).