diff options
| author | Jouni Malinen <j@w1.fi> | 2010-05-01 14:35:28 (GMT) |
|---|---|---|
| committer | Jouni Malinen <j@w1.fi> | 2010-10-04 06:35:08 (GMT) |
| commit | 1ab0b31aa626b6cb330628e7a281c5771dd5b851 (patch) | |
| tree | 9578e9586754a3fbea79053c023f714ac6a51a56 /src/drivers/driver_ndiswrapper.c | |
| parent | fb91cf5b56b43344bb6dfe208c458f2ffb253377 (diff) | |
| download | hostap-06-1ab0b31aa626b6cb330628e7a281c5771dd5b851.zip hostap-06-1ab0b31aa626b6cb330628e7a281c5771dd5b851.tar.gz hostap-06-1ab0b31aa626b6cb330628e7a281c5771dd5b851.tar.bz2 | |
Fix fallback from failed PMKSA caching into full EAP authentication
Commit 83935317a78fb4157eb6e5134527b9311dbf7b8c added forced
disconnection in case of 4-way handshake failures. However, it should
not have changed the case where the supplicant is requesting fallback
to full EAP authentication if the PMKID in EAPOL-Key message 1/4 is
not know. This case needs to send an EAPOL-Start frame instead of
EAPOL-Key message 2/4.
This works around a problem with APs that try to force PMKSA caching
even when the client does not include PMKID in (re)association request
frame to request it. [Bug 355]
(cherry picked from commit b4a1256d3660a2b5239062a9b42de79b8a34286a)
(cherry picked from commit a5277ad2a182e0264715533c11ed9a90296298e4)
Diffstat (limited to 'src/drivers/driver_ndiswrapper.c')
0 files changed, 0 insertions, 0 deletions