Pragaspathi Thilagaraj
e20af679d1
Userspace gives a connect request to the driver with bssid/bssid hint and if association reject is received from AP with reason invalid PMKID(53), then it means the previous PMKID cached is not valid and the STA has to do full SAE authentication to derive new PMK. When assoc reject is received from AP, and if no other candidate is found for connection, the driver sends nl80211 connection failed notification and the supplicant issues delete pmksa for that failed bssid, thereby preventing from trying to the same AP again with same stale pmkid. But after receiving assoc rejection, if other candidate is found, the driver tries to connect to the other BSS and if association fails with that too, the driver will send connect failed notification for the latest BSSID to which connection failed. So the PMKID for AP1, for which assoc reject was received due to invalid pmkid, is not deleted and when connect request for that AP is received again, the driver will try to do open auth with the stale PMKID. So delete the PMKID of SAE bssid when association rejection is received from the AP due to invalid PMKID. Change-Id: I2c7064b5cd333ccd166890bc4a6f7c8b8b9d503b CRs-Fixed: 2542232
This is CNSS WLAN Host Driver for products starting from iHelium