FW: [wpa_supplicant] Most WPA AP:s dont get to WPA_4WAY_HANDSHAKE state when wrong PSK is supplied

Olsson, Ola1 Ola1.Olsson at sonyericsson.com
Sat Dec 4 06:50:23 EST 2010


Hi,

For most WPA AP:s when using supplicant 0.6 with driver_wext and supplying the wrong PSK, I don't get the wpa_msg callback stating "pre-shared key may be incorrect" as the station is not in WPA_4WAY_HANDSHAKE state. There are APs where I actually do get this callback however...
According to the code, this is fully understandable as the wpa_supplicant_event_disassoc() in events.c is designed like this.

The behaviour I get in most cases is that I get my phone in state ASSOCIATING and then get EVENT_DISASSOC from wpa_driver_wext_event_wireless() in driver_wext.c after evaluating that the is_zero_ether_addr() evaluates to true.

My question is:
*Why don't we treat this 00:00:00:00:00:00 mac address as erroneous PSK even though we are only in ASSOCIATING state? When changing the code in events.c to also send the callback when in ASSOCIATING, it works perfectly. I'm a little bit worried of the side effects though. Anybody who knows what might go wrong?


Br Ola
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.shmoo.com/pipermail/hostap/attachments/20101204/7802c2e0/attachment.htm 


More information about the HostAP mailing list