ec5c39a557
It is now possible to optionally specify keyid for each wpa_psk_file entry: keyid=something 00:00:00:00:00:00 secretpassphrase When station connects and the passphrase it used has an associated keyid it will be appended to the AP-STA-CONNECTED event string: wlan0: AP-STA-CONNECTED 00:36:76:21:dc:7b keyid=something It's also possible to retrieve it through the control interface: $ hostapd_cli all_sta Selected interface 'ap0' 00:36:76:21:dc:7b ... keyid=something New hostapd is able to read old wpa_psk_file. However, old hostapd will not be able to read the new wpa_psk_file if it includes keyids. Signed-off-by: Michal Kazior <michal@plume.com>
13 lines
698 B
Plaintext
13 lines
698 B
Plaintext
# List of WPA PSKs. Each line, except for empty lines and lines starting
|
|
# with #, must contain a MAC address and PSK separated with a space.
|
|
# Special MAC address 00:00:00:00:00:00 can be used to configure PSKs that
|
|
# anyone can use. PSK can be configured as an ASCII passphrase of 8..63
|
|
# characters or as a 256-bit hex PSK (64 hex digits).
|
|
# An optional key identifier can be added by prefixing the line with
|
|
# keyid=<keyid_string>
|
|
00:00:00:00:00:00 secret passphrase
|
|
00:11:22:33:44:55 another passphrase
|
|
00:22:33:44:55:66 0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef
|
|
keyid=example_id 00:11:22:33:44:77 passphrase with keyid
|
|
00:00:00:00:00:00 another passphrase for all STAs
|