From: Kalle Valo <kvalo@kernel.org>
To: Arend Van Spriel <arend.vanspriel@broadcom.com>
Cc: Hector Martin <marcan@marcan.st>,
Arend van Spriel <aspriel@gmail.com>,
Franky Lin <franky.lin@broadcom.com>,
Hante Meuleman <hante.meuleman@broadcom.com>,
Daniel Berlin <dberlin@dberlin.org>,
<linux-wireless@vger.kernel.org>,
<brcm80211-dev-list.pdl@broadcom.com>,
<SHA-cyfmac-dev-list@infineon.com>,
<linux-kernel@vger.kernel.org>, <asahi@lists.linux.dev>
Subject: Re: [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password
Date: Tue, 19 Dec 2023 10:57:17 +0200 [thread overview]
Message-ID: <877clash76.fsf@kernel.org> (raw)
In-Reply-To: <18c80d15e30.279b.9b12b7fc0a3841636cfb5e919b41b954@broadcom.com> (Arend Van Spriel's message of "Tue, 19 Dec 2023 09:52:23 +0100")
Arend Van Spriel <arend.vanspriel@broadcom.com> writes:
> On December 17, 2023 12:25:23 PM Kalle Valo <kvalo@kernel.org> wrote:
>
>> Hector Martin <marcan@marcan.st> wrote:
>>
>>> Using the WSEC command instead of sae_password seems to be the supported
>>> mechanism on newer firmware, and also how the brcmdhd driver does it.
>>>
>>> According to user reports [1], the sae_password codepath doesn't actually
>>> work on machines with Cypress chips anyway, so no harm in removing it.
>>>
>>> This makes WPA3 work with iwd, or with wpa_supplicant pending a support
>>> patchset [2].
>>>
>>> [1] https://rachelbythebay.com/w/2023/11/06/wpa3/
>>> [2] http://lists.infradead.org/pipermail/hostap/2023-July/041653.html
>>>
>>> Signed-off-by: Hector Martin <marcan@marcan.st>
>>> Reviewed-by: Neal Gompa <neal@gompa.dev>
>>
>> Arend, what do you think?
>>
>> We recently talked about people testing brcmfmac patches, has anyone else
>> tested this?
>
> Not sure I already replied so maybe I am repeating myself. I would
> prefer to keep the Cypress sae_password path as well although it
> reportedly does not work. The vendor support in the driver can be used
> to accommodate for that. The other option would be to have people with
> Cypress chipset test this patch. If that works for both we can
> consider dropping the sae_password path.
Ok, thanks for checking.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2023-12-19 8:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 6:05 [PATCH] wifi: brcmfmac: cfg80211: Use WSEC to set SAE password Hector Martin
2023-11-08 11:12 ` Neal Gompa
2023-12-17 11:25 ` Kalle Valo
2023-12-19 8:52 ` Arend Van Spriel
2023-12-19 8:57 ` Kalle Valo [this message]
2023-12-19 11:01 ` Hector Martin
2023-12-19 13:46 ` Arend van Spriel
2023-12-19 14:26 ` Julian Calaby
2023-12-21 20:39 ` Marcel Holtmann
2023-12-22 0:03 ` Neal Gompa
2023-12-22 6:16 ` Marcel Holtmann
2023-12-24 9:03 ` Arend van Spriel
[not found] ` <CAF4BwTXNtu30DAgBXo4auDaDK0iWc9Ch8f=EH+facQ-_F-oMUQ@mail.gmail.com>
2023-12-19 14:42 ` Kalle Valo
2023-12-20 0:06 ` Hector Martin
2023-12-20 1:44 ` Linus Torvalds
2023-12-20 4:16 ` Hector Martin
2023-12-20 11:05 ` Bagas Sanjaya
2023-12-20 10:20 ` Kalle Valo
2023-12-20 15:55 ` Kalle Valo
2023-12-20 16:42 ` Eric Curtin
2023-12-20 18:14 ` Hector Martin
2023-12-20 19:36 ` Arend van Spriel
2023-12-21 0:49 ` Hector Martin
2023-12-21 9:57 ` Arend van Spriel
2023-12-22 5:10 ` Hector Martin
2023-12-22 12:25 ` Eric Curtin
2024-01-07 9:51 ` Arend van Spriel
2023-12-20 11:32 ` Eric Curtin
2023-12-20 10:16 ` Paul Fertser
2023-12-20 18:02 ` Hector Martin
2023-12-21 14:04 ` Arend van Spriel
2023-12-21 14:11 ` Arend van Spriel
2023-12-22 5:35 ` Hector Martin
2023-12-22 5:28 ` Hector Martin
2023-12-22 7:30 ` Arend Van Spriel
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=877clash76.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=SHA-cyfmac-dev-list@infineon.com \
--cc=arend.vanspriel@broadcom.com \
--cc=asahi@lists.linux.dev \
--cc=aspriel@gmail.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=dberlin@dberlin.org \
--cc=franky.lin@broadcom.com \
--cc=hante.meuleman@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marcan@marcan.st \
/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