From 240e9af4d1fc46bf13edf7639ddda2bd25488e7c Mon Sep 17 00:00:00 2001 From: Jouni Malinen Date: Fri, 31 Jul 2020 19:59:52 +0300 Subject: [PATCH] SAE-PK: Make no-KEK debug prints distinct Debug logs did not make it clear whether the failure happens when checking a received SAE confirm or when writing own SAE confirm. Those cases have different checks on when to go through SAE-PK processing, so it is useful to make this part clear in the debug log. Signed-off-by: Jouni Malinen --- src/common/sae_pk.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/common/sae_pk.c b/src/common/sae_pk.c index b1c35d100..cd0ccb729 100644 --- a/src/common/sae_pk.c +++ b/src/common/sae_pk.c @@ -403,7 +403,8 @@ int sae_write_confirm_pk(struct sae_data *sae, struct wpabuf *buf) #endif /* CONFIG_TESTING_OPTIONS */ if (tmp->kek_len != 32 && tmp->kek_len != 48 && tmp->kek_len != 64) { - wpa_printf(MSG_INFO, "SAE-PK: No KEK available for confirm"); + wpa_printf(MSG_INFO, + "SAE-PK: No KEK available for writing confirm"); return -1; } @@ -580,7 +581,8 @@ int sae_check_confirm_pk(struct sae_data *sae, const u8 *ies, size_t ies_len) return 0; if (tmp->kek_len != 32 && tmp->kek_len != 48 && tmp->kek_len != 64) { - wpa_printf(MSG_INFO, "SAE-PK: No KEK available for confirm"); + wpa_printf(MSG_INFO, + "SAE-PK: No KEK available for checking confirm"); return -1; }