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>
This commit is contained in:
parent
9d00efd829
commit
240e9af4d1
1 changed files with 4 additions and 2 deletions
|
@ -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;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue