From: Michal Kazior <michal@xxxxxxxxx>
Hostapd was already exposing this. There's no
reason not to expose it in wpa_supplicant.
This allows 3rd party apps interacting with the
control interface to handle DPP events to get
configs instead of needing to dance around with
update_config=1 and save_config.
Signed-off-by: Michal Kazior <michal@xxxxxxxxx>
---
wpa_supplicant/dpp_supplicant.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/wpa_supplicant/dpp_supplicant.c b/wpa_supplicant/dpp_supplicant.c
index 910602e34..01e7fce26 100644
--- a/wpa_supplicant/dpp_supplicant.c
+++ b/wpa_supplicant/dpp_supplicant.c
@@ -1441,6 +1441,8 @@ static int wpas_dpp_handle_config_obj(struct wpa_supplicant *wpa_s,
struct dpp_config_obj *conf)
{
wpa_msg(wpa_s, MSG_INFO, DPP_EVENT_CONF_RECEIVED);
+ wpa_msg(wpa_s, MSG_INFO, DPP_EVENT_CONFOBJ_AKM "%s",
+ dpp_akm_str(conf->akm));
if (conf->ssid_len)
wpa_msg(wpa_s, MSG_INFO, DPP_EVENT_CONFOBJ_SSID "%s",
wpa_ssid_txt(conf->ssid, conf->ssid_len));
--
2.27.0
_______________________________________________
Hostap mailing list
Hostap@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/hostap
