mirror of
https://git.kernel.org/pub/scm/network/wireless/iwd.git
synced 2024-11-22 14:49:24 +01:00
TODO: Mark handle 2nd RSNE task done
This commit is contained in:
parent
6db43588c6
commit
307bea844a
12
TODO
12
TODO
@ -293,18 +293,6 @@ Wireless daemon
|
||||
Priority: Medium
|
||||
Complexity: C1
|
||||
|
||||
- Parse & utilize the 2nd RSNE element in Step 3/4 of the 4-way Handshake
|
||||
|
||||
EAPoL Key Data can contain two RSN elements. The second element contains
|
||||
ciphering settings which were mandated by the AP and could be different
|
||||
from settings we provided. We should parse the 2nd RSNE and determine
|
||||
whether the settings are acceptable. If so, these settings should be
|
||||
utilized for the established connection. Otherwise, connection establishment
|
||||
should be aborted.
|
||||
|
||||
Priority: High
|
||||
Complexity: C1
|
||||
|
||||
- Add unit test for each of the mpdu management frame type
|
||||
|
||||
Currently, only authentication and deauthentication frames have
|
||||
|
@ -2,25 +2,28 @@
|
||||
IWD
|
||||
===
|
||||
|
||||
IWD will start a scheduled scan to the interface if the hardware supports
|
||||
- IWD will start a scheduled scan to the interface if the hardware supports
|
||||
that feature. If the iwd closes or dies so that the kernel netlink socket
|
||||
is closed, then the scheduled scan is cancelled automatically if the kernel
|
||||
supports this. This is done by giving NL80211_ATTR_SOCKET_OWNER netlink
|
||||
attribute when initiating the scheduled scan.
|
||||
|
||||
IWD contains a network object that will contain a list of BSS that have the
|
||||
- IWD contains a network object that will contain a list of BSS that have the
|
||||
same SSID and security setting. From user point of view, we will connect to
|
||||
a certain SSID instead of connecting directly to a BSS. IWD will then pick
|
||||
the best BSS automatically from the BSS list when connecting to a SSID.
|
||||
The "best" BSS in this context is the BSS that has the highest signal strength.
|
||||
|
||||
IWD uses the DBus agent interface to query information from the user.
|
||||
- IWD uses the DBus agent interface to query information from the user.
|
||||
The information asked include things like passphrase etc. The user can
|
||||
register only one agent to iwd. If the user does not respond in timely
|
||||
manner to the query, then the pending user request is cancelled after a
|
||||
timeout. The pending user request is also cancelled if user disconnects a
|
||||
pending connection attempt.
|
||||
|
||||
- IWD supports the full RSN 4-Way Handshake for PTK generation. Support for
|
||||
handling the optional (second) RSN element from the AP is included.
|
||||
|
||||
|
||||
Wireless monitor
|
||||
================
|
||||
|
Loading…
Reference in New Issue
Block a user