DPP2: Clear requirement for QR Code mutual authentication for chirping

The chirping cases are not really targeting interactive operations, so
clear the requirement for mutual authentication when DPP_CHIRP command
is used. This avoids testing isues where an earlier DPP_LISTEN command
has used qr=mutual parameter and that seting not getting cleared before
the next DPP_CHIRP command is used.

This fixes a test case failure in the following test sequence:
dpp_auth_resp_status_failure dpp_controller_relay_chirp

Signed-off-by: Jouni Malinen <jouni@codeaurora.org>

diff --git a/wpa_supplicant/dpp_supplicant.c b/wpa_supplicant/dpp_supplicant.c
index 45fd3a744495c192212b0c4a174f7c1d69669bb2..e578e0aefb4c8bec7fa2f8e28e02590f57a81e3b 100644 (file)
--- a/wpa_supplicant/dpp_supplicant.c
+++ b/wpa_supplicant/dpp_supplicant.c
@@ -3020,6 +3020,7 @@ int wpas_dpp_chirp(struct wpa_supplicant *wpa_s, const char *cmd)
 
        wpas_dpp_chirp_stop(wpa_s);
        wpa_s->dpp_allowed_roles = DPP_CAPAB_ENROLLEE;
+       wpa_s->dpp_qr_mutual = 0;
        wpa_s->dpp_chirp_bi = bi;
        wpa_s->dpp_presence_announcement = dpp_build_presence_announcement(bi);
        if (!wpa_s->dpp_presence_announcement)