mirror of
https://git.kernel.org/pub/scm/network/wireless/iwd.git
synced 2025-05-07 10:27:26 +02:00
wiphy: check SAE offload in wiphy_can_connect
This allows this wiphy_can_connect to pass for an SAE BSS if the hardware does not support user space SAE, but does support SAE offload.
This commit is contained in:
parent
3e3ef284de
commit
997c54f185
10
src/wiphy.c
10
src/wiphy.c
@ -411,15 +411,7 @@ bool wiphy_can_connect(struct wiphy *wiphy, struct scan_bss *bss)
|
|||||||
switch (rsn_info.akm_suites) {
|
switch (rsn_info.akm_suites) {
|
||||||
case IE_RSN_AKM_SUITE_SAE_SHA256:
|
case IE_RSN_AKM_SUITE_SAE_SHA256:
|
||||||
case IE_RSN_AKM_SUITE_FT_OVER_SAE_SHA256:
|
case IE_RSN_AKM_SUITE_FT_OVER_SAE_SHA256:
|
||||||
/*
|
if (!wiphy_can_connect_sae(wiphy))
|
||||||
* if the AP ONLY supports SAE/WPA3, then we can only
|
|
||||||
* connect if the wiphy feature is supported. Otherwise
|
|
||||||
* the AP may list SAE as one of the AKM's but also
|
|
||||||
* support PSK (hybrid). In this case we still want to
|
|
||||||
* allow a connection even if SAE is not supported.
|
|
||||||
*/
|
|
||||||
if (!wiphy_has_feature(wiphy, NL80211_FEATURE_SAE) ||
|
|
||||||
!wiphy->support_cmds_auth_assoc)
|
|
||||||
return false;
|
return false;
|
||||||
|
|
||||||
break;
|
break;
|
||||||
|
Loading…
x
Reference in New Issue
Block a user