DPP: Expose config object AKM in wpa_supplicant control interface

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@plume.com>

diff --git a/wpa_supplicant/dpp_supplicant.c b/wpa_supplicant/dpp_supplicant.c
index 8df938db40d9ffe6ef7a1de5154ea0d4b658bfee..282b6cd7534ee1dbbe99bca96cc1d0c61cc5bde4 100644 (file)
--- a/wpa_supplicant/dpp_supplicant.c
+++ b/wpa_supplicant/dpp_supplicant.c
@@ -1443,6 +1443,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));