[PATCHv2 3/3] DPP: expose own and peer bootstrap info ids on dpp auth

[Michal Kazior]

From: Michal Kazior <michal at plume.com>

The system may be interested in knowing which
bootstrap information entries are being exercised.

This could be used for statistics or completion
signaling to upper application layer outside of
hostapd, along with the public key hash.

Signed-off-by: Michal Kazior <michal at plume.com>
---

Notes:
    v2:
     - added to allow bootstrap -- pk hash mapping

 src/common/dpp.c | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/src/common/dpp.c b/src/common/dpp.c
index e1edde449..2b6844e52 100644
--- a/src/common/dpp.c
+++ b/src/common/dpp.c
@@ -4433,8 +4433,11 @@ void dpp_notify_auth_success(struct dpp_authentication *auth, int initiator)
 	os_memset(hex, 0, sizeof(hex));
 	dpp_get_pubkey_hash(auth->peer_protocol_key, hex, sizeof(hex));
 
-	wpa_msg(auth->msg_ctx, MSG_INFO, DPP_EVENT_AUTH_SUCCESS "init=%d pkhash=%s",
-		initiator, hex);
+	wpa_msg(auth->msg_ctx, MSG_INFO, DPP_EVENT_AUTH_SUCCESS
+		"init=%d pkhash=%s own=%d peer=%d",
+		initiator, hex,
+		auth->own_bi ? auth->own_bi->id : -1,
+		auth->peer_bi ? auth->peer_bi->id : -1);
 }
 
 #endif /* CONFIG_DPP2 */
-- 
2.27.0