Wep Problem When WPS is active
ilhancan at gmail.com
Mon Sep 14 11:28:58 EDT 2009
I applied the patch and nothing has changed regarding windows xp sp2/3 clients.
> Is that a recent snapshot of the hostapd development branch or something
> potentially older?
Its not a recent git, I fetched it at the end of February, before your
> I did add a partial workaround for this in March:
After applying this, I found out that (after sniffing the probe
responses) Microsoft OUI is not recognized properly (by 2 different
sniffers and another hostapd AP [telling me WPS overflow due to
confusion]) since it is still a part of WPS IE. I will try adding that
IE as an independent IE and see if that changes anything.
> There is not really much else that can be done to work around this
> unless you are willing to replace all the client devices with something
> that handles WPS networks with WEP more gracefully. Or better yet, get
> rid of that WEP configuration in the first place; as far as security is
> concerned, it is about as good as leaving the network open anyway.
Unfortunately I do not have the luxury to modify clients or restrict
WEP totally even though its security is reliable in the order of
minutes. Its still people's choice.
By the way, I experienced another problem similar to this while
playing with Intel Proset Supplicant and WPA/WPA2. Most of the time,
when I double click the AP from Proset Supplicant's list (for the
first time), it directly asks a passphrase for WPA/WPA2. However,
sometimes, it asks me to wait till supplicant automatically gathers
the encryption and after 10-15secs, it warns me that there may be
802.1x but the credentials couldnt be fetched properly.
Its probably the same problem but you may have an idea about this
issue. I was using the latest proset/intel 2200 driver with windows xp
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the HostAP