Check for LEAP before doing FT
According to https://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/80211r-ft/b-80211r-dg.html Cisco does not support EAP-LEAP with Fast Transition. Here, we check for LEAP before selecting FT 802.1X key management suite. Signed-off-by: Matthew Wang <matthewmwang@chromium.org>
This commit is contained in:
parent
ba2d5f3642
commit
dd0153fced
1 changed files with 4 additions and 2 deletions
|
@ -1413,7 +1413,8 @@ int wpa_supplicant_set_suites(struct wpa_supplicant *wpa_s,
|
||||||
if (0) {
|
if (0) {
|
||||||
#ifdef CONFIG_IEEE80211R
|
#ifdef CONFIG_IEEE80211R
|
||||||
#ifdef CONFIG_SHA384
|
#ifdef CONFIG_SHA384
|
||||||
} else if (sel & WPA_KEY_MGMT_FT_IEEE8021X_SHA384) {
|
} else if ((sel & WPA_KEY_MGMT_FT_IEEE8021X_SHA384) &&
|
||||||
|
os_strcmp(wpa_supplicant_get_eap_mode(wpa_s), "LEAP") != 0) {
|
||||||
wpa_s->key_mgmt = WPA_KEY_MGMT_FT_IEEE8021X_SHA384;
|
wpa_s->key_mgmt = WPA_KEY_MGMT_FT_IEEE8021X_SHA384;
|
||||||
wpa_dbg(wpa_s, MSG_DEBUG,
|
wpa_dbg(wpa_s, MSG_DEBUG,
|
||||||
"WPA: using KEY_MGMT FT/802.1X-SHA384");
|
"WPA: using KEY_MGMT FT/802.1X-SHA384");
|
||||||
|
@ -1456,7 +1457,8 @@ int wpa_supplicant_set_suites(struct wpa_supplicant *wpa_s,
|
||||||
wpa_dbg(wpa_s, MSG_DEBUG, "WPA: using KEY_MGMT FILS-SHA256");
|
wpa_dbg(wpa_s, MSG_DEBUG, "WPA: using KEY_MGMT FILS-SHA256");
|
||||||
#endif /* CONFIG_FILS */
|
#endif /* CONFIG_FILS */
|
||||||
#ifdef CONFIG_IEEE80211R
|
#ifdef CONFIG_IEEE80211R
|
||||||
} else if (sel & WPA_KEY_MGMT_FT_IEEE8021X) {
|
} else if ((sel & WPA_KEY_MGMT_FT_IEEE8021X) &&
|
||||||
|
os_strcmp(wpa_supplicant_get_eap_mode(wpa_s), "LEAP") != 0) {
|
||||||
wpa_s->key_mgmt = WPA_KEY_MGMT_FT_IEEE8021X;
|
wpa_s->key_mgmt = WPA_KEY_MGMT_FT_IEEE8021X;
|
||||||
wpa_dbg(wpa_s, MSG_DEBUG, "WPA: using KEY_MGMT FT/802.1X");
|
wpa_dbg(wpa_s, MSG_DEBUG, "WPA: using KEY_MGMT FT/802.1X");
|
||||||
if (!ssid->ft_eap_pmksa_caching &&
|
if (!ssid->ft_eap_pmksa_caching &&
|
||||||
|
|
Loading…
Reference in a new issue