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 <jouni@codeaurora.org>

diff --git a/src/common/sae_pk.c b/src/common/sae_pk.c
index b1c35d100a7cdb4ff82092804bb6f6da87a8f610..cd0ccb729ae16fbf2434b918fc340d6ea0e3bf06 100644 (file)
--- 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;
        }