diff options
| author | Amitkumar Karwar <akarwar@marvell.com> | 2011-04-01 18:36:46 -0700 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2011-04-07 15:34:12 -0400 |
| commit | 2d3d0a88bd136f8e6f39bc53242712852e5d0bb2 (patch) | |
| tree | 1c7f5b477ccfc20fe8a1e12c8c997a87c2bd0df5 /drivers/net/wireless/mwifiex/sta_event.c | |
| parent | f4263c9857e6411ef2388868cc6c79a1602a654e (diff) | |
| download | kernel_samsung_smdk4412-2d3d0a88bd136f8e6f39bc53242712852e5d0bb2.zip kernel_samsung_smdk4412-2d3d0a88bd136f8e6f39bc53242712852e5d0bb2.tar.gz kernel_samsung_smdk4412-2d3d0a88bd136f8e6f39bc53242712852e5d0bb2.tar.bz2 | |
mwifiex: return success in set_default_key for WPA/WPA2
When testing wpa_supplicant with 'nl80211' driver to connect
to an AP with WPA/WPA2 security, we notice the followings:
1) add_key is called firstly with the key from cfg80211
2) set_defaut_key is called next
set_default_key() is specific to WEP keys and should not be
called in case of WPA/WPA2 security. The set_default_key()
won't be called if wpa_supplicant uses "-Dwext" option,
but it's been called if "-Dnl80211" option is specified.
We can fix this issue by adding a check to return from
set_default_key() if WEP key is not configured.
Signed-off-by: Amitkumar Karwar <akarwar@marvell.com>
Signed-off-by: Yogesh Ashok Powar <yogeshp@marvell.com>
Signed-off-by: Marc Yang <yangyang@marvell.com>
Signed-off-by: Bing Zhao <bzhao@marvell.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/mwifiex/sta_event.c')
0 files changed, 0 insertions, 0 deletions