Do not clear PMKSA cache on all network block parameter changes

The bssid and priority parameters in a network block do not have any
effect on the validity of a PMKSA cache entry, so avoid flushing the
PMKSA cache when only these parameters are changed. This is mainly
to allow forced roaming or network selection changes without causing
a disconnection if the changes are done during RSN association that
used EAP.

Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>

diff --git a/wpa_supplicant/ctrl_iface.c b/wpa_supplicant/ctrl_iface.c
index 3a4364a595a416361f7002b323ab4e13014832a5..75e92a945828f778ad5423b2437ec7b043439165 100644 (file)
--- a/wpa_supplicant/ctrl_iface.c
+++ b/wpa_supplicant/ctrl_iface.c
@@ -2056,7 +2056,9 @@ static int wpa_supplicant_ctrl_iface_set_network(
                return -1;
        }
 
-       wpa_sm_pmksa_cache_flush(wpa_s->wpa, ssid);
+       if (os_strcmp(name, "bssid") != 0 &&
+           os_strcmp(name, "priority") != 0)
+               wpa_sm_pmksa_cache_flush(wpa_s->wpa, ssid);
 
        if (wpa_s->current_ssid == ssid || wpa_s->current_ssid == NULL) {
                /*