Vinayak Yadawad <vinayak.yadawad@xxxxxxxxxxxx> 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@xxxxxxxxxxxx>
[...]
> @@ -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
