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>
This commit is contained in:
parent
e4e95aabbf
commit
2e956c37d2
1 changed files with 1 additions and 1 deletions
|
@ -661,7 +661,7 @@ static int dpp_controller_rx_auth_resp(struct dpp_connection *conn,
|
||||||
if (auth->auth_resp_status == DPP_STATUS_RESPONSE_PENDING) {
|
if (auth->auth_resp_status == DPP_STATUS_RESPONSE_PENDING) {
|
||||||
wpa_printf(MSG_DEBUG,
|
wpa_printf(MSG_DEBUG,
|
||||||
"DPP: Start wait for full response");
|
"DPP: Start wait for full response");
|
||||||
return -1;
|
return 0;
|
||||||
}
|
}
|
||||||
wpa_printf(MSG_DEBUG, "DPP: No confirm generated");
|
wpa_printf(MSG_DEBUG, "DPP: No confirm generated");
|
||||||
dpp_connection_remove(conn);
|
dpp_connection_remove(conn);
|
||||||
|
|
Loading…
Reference in a new issue