From: Michal Kazior <michal@xxxxxxxxx> This has been prompted by the thread on the mailing list "dynamically added/removed PSKs without MAC pairing". I've originally did these patches for an older hostapd tree quite some time ago. For various reasons I didn't upstream them until now. I've had to rebase and rework them a bit but hopefully I didn't mess anything up. I guess it's a little iffy to expose PMK in cli/logs. I was considering using explicit tags/aliases in wpa_psk_file in the format of `tag mac psk`, e.g. tag_1 00:00:00:00:00:00 secretpassword tag_2 00:00:00:00:00:00 different111 But asked myself if it's really more secure or is it just unnecessarily complex. FWIW The tag could be made optional so old wpa_psk_file format would remain working with no changes. Thoughts? Michal Kazior (2): AP: keep track and expose WPA-PSK PMK info of each station AP: add wpa_psk_file reloading in runtime hostapd/ctrl_iface.c | 61 +++++++++++++++++++++++++++++++++++++++++++ hostapd/hostapd_cli.c | 9 +++++++ src/ap/sta_info.c | 28 ++++++++++++++++++++ src/ap/wpa_auth.c | 18 +++++++++++++ src/ap/wpa_auth.h | 1 + src/ap/wpa_auth_ft.c | 2 ++ src/common/wpa_ctrl.h | 1 + 7 files changed, 120 insertions(+) -- 2.19.1 _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
