diff options
| author | James Prestwood <prestwoj@gmail.com> | 2020-04-13 19:20:53 +0300 |
|---|---|---|
| committer | Johannes Berg <johannes.berg@intel.com> | 2020-08-27 12:29:59 +0300 |
| commit | 493a0ebd804c986e6bd207603c5e1ca748470d3d (patch) | |
| tree | dff6ea46fe44856b1662ec4058b69a3ab8467720 /include/net | |
| parent | 12adee3c467dd3dff9f0cd98a33f26dad61187cc (diff) | |
| download | linux-493a0ebd804c986e6bd207603c5e1ca748470d3d.tar.xz | |
nl80211: fix PORT_AUTHORIZED wording to reflect behavior
The CMD_PORT_AUTHORIZED event was described as an event which indicated
a successfully completed 4-way handshake. But the behavior was
not as advertized. The only driver which uses this is brcmfmac, and
this driver only sends the event after a successful 802.1X-FT roam.
This prevents userspace applications from knowing if the 4-way completed
on:
1. Normal 802.1X connects
2. Normal PSK connections
3. FT-PSK roams
wpa_supplicant handles this incorrect behavior by just completing
the connection after association, before the 4-way has completed.
If the 4-way ends up failing it disconnects at that point.
Since this behavior appears to be expected (wpa_s handles it this
way) I have changed the wording in the API description to reflect the
actual behavior.
Signed-off-by: James Prestwood <prestwoj@gmail.com>
Link: https://lore.kernel.org/r/20200413162053.3711-1-prestwoj@gmail.com
[fix spelling of 802.1X throughout ...]
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'include/net')
0 files changed, 0 insertions, 0 deletions
