All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Vinayak Yadawad <vinayak.yadawad@broadcom.com>
Cc: johannes@sipsolutions.net,  linux-wireless@vger.kernel.org,
	jithu.jance@broadcom.com
Subject: Re: [PATCH 1/1] wifi: nl80211: Add support for plumbing SAE groups to driver
Date: Mon, 12 Feb 2024 09:25:54 +0200	[thread overview]
Message-ID: <87mss6f8jh.fsf@kernel.org> (raw)
In-Reply-To: <309965e8ef4d220053ca7e6bd34393f892ea1bb8.1707486287.git.vinayak.yadawad@broadcom.com> (Vinayak Yadawad's message of "Fri, 9 Feb 2024 19:20:43 +0530")

Vinayak Yadawad <vinayak.yadawad@broadcom.com> writes:

> In case of SAE authentication offload, the driver would need
> the info of SAE DH groups for both STA connection and soft AP.
> In the current change we update the SAE DH group support info
> to driver in the order/priority as provided by the supplicant/
> upper layer.
>
> Signed-off-by: Vinayak Yadawad <vinayak.yadawad@broadcom.com>

[...]

> @@ -1235,6 +1236,9 @@ struct survey_info {
>   *
>   *	NL80211_SAE_PWE_BOTH
>   *	  Allow either hunting-and-pecking loop or hash-to-element
> + *
> + * @sae_dh_groups: SAE DH groups in preference order.
> + * @n_sae_dhd_groups: No of SAE DH groups assigned.
>   */
>  struct cfg80211_crypto_settings {
>  	u32 wpa_versions;
> @@ -1252,6 +1256,8 @@ struct cfg80211_crypto_settings {
>  	const u8 *sae_pwd;
>  	u8 sae_pwd_len;
>  	enum nl80211_sae_pwe_mechanism sae_pwe;
> +	u32 sae_dh_groups[CFG80211_MAX_NUM_SAE_DH_GROUPS];
> +	u8 n_sae_dh_groups;
>  };

What driver is going to use these new crypto settings? Or is this for an
out-of-tree driver?

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  parent reply	other threads:[~2024-02-12  7:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 13:50 [PATCH 1/1] wifi: nl80211: Add support for plumbing SAE groups to driver Vinayak Yadawad
2024-02-10  1:01 ` Jeff Johnson
2024-02-11 19:08   ` Johannes Berg
2024-02-12  7:25 ` Kalle Valo [this message]
2024-02-12 19:58   ` Johannes Berg
2024-02-13  9:42     ` Arend van Spriel
2024-02-13 10:09       ` Johannes Berg
2024-02-13 11:13         ` Arend van Spriel
2024-02-13 11:45           ` Johannes Berg
2024-02-13 12:19             ` Arend van Spriel
2024-02-13 12:30               ` Johannes Berg
2024-02-13 12:50                 ` Kalle Valo
2024-02-13 13:43                   ` Jithu Jance
2024-02-13 12:46     ` Kalle Valo
2024-02-14  1:43     ` Jakub Kicinski
2024-02-14 10:27       ` Johannes Berg
2024-02-14 16:08         ` Jakub Kicinski
2024-02-14 16:57         ` Jeff Johnson
2024-02-27 19:27           ` Johannes Berg

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=87mss6f8jh.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=jithu.jance@broadcom.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=vinayak.yadawad@broadcom.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.