You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
215b4d8a72
wpa_supplicant disables PMKSA caching with FT-EAP by default due to known interoperability issues with APs. This is allowed only if the network profile is explicitly enabling caching with ft_eap_pmksa_caching=1. However, the PMKID for such PMKSA cache entries was still being configured to the driver and it was possible for the driver to build an RSNE with the PMKID for SME-in-driver cases. This could result in hitting the interop issue with some APs. Fix this by skipping PMKID configuration to the driver fot FT-EAP AKM if ft_eap_pmksa_caching=1 is not used in the network profile so that the driver and wpa_supplicant behavior are in sync for this. Signed-off-by: Jouni Malinen <jouni@codeaurora.org> |
4 years ago | |
---|---|---|
.. | ||
ap | 4 years ago | |
common | 4 years ago | |
crypto | 4 years ago | |
drivers | 4 years ago | |
eap_common | 5 years ago | |
eap_peer | 4 years ago | |
eap_server | 4 years ago | |
eapol_auth | 4 years ago | |
eapol_supp | 4 years ago | |
fst | 4 years ago | |
l2_packet | 4 years ago | |
p2p | 4 years ago | |
pae | 4 years ago | |
radius | 4 years ago | |
rsn_supp | 4 years ago | |
tls | 4 years ago | |
utils | 4 years ago | |
wps | 4 years ago | |
Makefile | 9 years ago | |
lib.rules | 5 years ago |