orinoco: fix TKIP countermeasure behaviour
authorDavid Kilroy <kilroyd@googlemail.com>
Sun, 5 Dec 2010 15:43:55 +0000 (15:43 +0000)
committerJohn W. Linville <linville@tuxdriver.com>
Wed, 8 Dec 2010 20:24:06 +0000 (15:24 -0500)
commit0a54917c3fc295cb61f3fb52373c173fd3b69f48
treee79be4b9595a05f7b47e6b840cbb35aea945f57b
parentba34fcee476d11e7c9df95932787a22a96ff6e68
orinoco: fix TKIP countermeasure behaviour

Enable the port when disabling countermeasures, and disable it on
enabling countermeasures.

This bug causes the response of the system to certain attacks to be
ineffective.

It also prevents wpa_supplicant from getting scan results, as
wpa_supplicant disables countermeasures on startup - preventing the
hardware from scanning.

wpa_supplicant works with ap_mode=2 despite this bug because the commit
handler re-enables the port.

The log tends to look like:

State: DISCONNECTED -> SCANNING
Starting AP scan for wildcard SSID
Scan requested (ret=0) - scan timeout 5 seconds
EAPOL: disable timer tick
EAPOL: Supplicant port status: Unauthorized
Scan timeout - try to get results
Failed to get scan results
Failed to get scan results - try scanning again
Setting scan request: 1 sec 0 usec
Starting AP scan for wildcard SSID
Scan requested (ret=-1) - scan timeout 5 seconds
Failed to initiate AP scan.

Reported by: Giacomo Comes <comes@naic.edu>
Signed-off by: David Kilroy <kilroyd@googlemail.com>
Cc: stable@kernel.org
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/orinoco/wext.c