summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorJames Prestwood <prestwoj@gmail.com>2020-04-13 18:20:53 +0200
committerJohannes Berg <johannes.berg@intel.com>2020-08-27 11:29:59 +0200
commit493a0ebd804c986e6bd207603c5e1ca748470d3d (patch)
treedff6ea46fe44856b1662ec4058b69a3ab8467720 /net
parentcfg80211: add helper fn for adjacent rule channels (diff)
downloadlinux-493a0ebd804c986e6bd207603c5e1ca748470d3d.tar.xz
linux-493a0ebd804c986e6bd207603c5e1ca748470d3d.zip
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 'net')
0 files changed, 0 insertions, 0 deletions