From: Jouni Malinen Date: Tue, 9 Oct 2012 10:06:37 +0000 (+0300) Subject: Do not clear PMKSA cache on all network block parameter changes X-Git-Tag: hostap_2_0~178 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d86a33853efe9bb3c09c4431fa77673620649c05;p=thirdparty%2Fhostap.git 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 --- diff --git a/wpa_supplicant/ctrl_iface.c b/wpa_supplicant/ctrl_iface.c index 3a4364a59..75e92a945 100644 --- 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) { /*