should ask for new key when wpa3-personal password is error
when wpa3-personal(sae) has wrong password, authenticate will failed.
At this time, new password is needed, so I think GetSecrets should be called again to get new password.
Since now, we can find such code
static gboolean
need_new_wpa_psk(NMDeviceWifi *self,
NMSupplicantInterfaceState old_state,
int disconnect_reason,
const char **setting_name)
{
/* A bad PSK will cause the supplicant to disconnect during the 4-way handshake */
if (old_state != NM_SUPPLICANT_INTERFACE_STATE_4WAY_HANDSHAKE)
return FALSE;
if (g_strcmp0(key_mgmt, "wpa-psk") == 0) {
}
}
When wpa3-personal authenticate failed, wpa usually failed in authentication state according to IEEE 802.11 SAE.
But NM seems dont deal with this situation.
So GetSecrets will not be called to ask for new key, authentication failed directly.
I think wpa3-personal is similar to wpa-psk, means it is not complicated AP(diff with enterprise network, with many same name APs), so I think it is ok to ask for new key. Also, i think it is better to do so.