DPP2: Do not close TCP socket when waiting for full Auth Resp

The case where mutual authentication with QR Code bootstrapping is used
with scanning of the QR Code during the exchange resulted in the
Controller closing the TCP socket too early. Fix this by leaving the
socket open while waiting for the full Authentication Response message.

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

diff --git a/src/common/dpp_tcp.c b/src/common/dpp_tcp.c
index 53fe67f81444fb9a12a3bbd7a9a17a90a9a4527a..90dd38fc0eee8674a6ca91b220d87fbf612abba9 100644 (file)
--- a/src/common/dpp_tcp.c
+++ b/src/common/dpp_tcp.c
@@ -661,7 +661,7 @@ static int dpp_controller_rx_auth_resp(struct dpp_connection *conn,
                if (auth->auth_resp_status == DPP_STATUS_RESPONSE_PENDING) {
                        wpa_printf(MSG_DEBUG,
                                   "DPP: Start wait for full response");
-                       return -1;
+                       return 0;
                }
                wpa_printf(MSG_DEBUG, "DPP: No confirm generated");
                dpp_connection_remove(conn);