Call expect_flight and received_flight in the 1.3 logic.
This doesn't do anything since they're for DTLS, but we ought to satisfy
the API nonetheless. expect_flight is easy with
ssl_hs_flush_and_read_message. received_flight I think basically needs
to get sprinkled into the state machine.
Change-Id: I406c7f776ad8e5e3cbcafcac6b26a688c6d3caf1
Reviewed-on: https://boringssl-review.googlesource.com/8883
Reviewed-by: Steven Valdez <svaldez@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
diff --git a/ssl/tls13_client.c b/ssl/tls13_client.c
index ead5b82..742dcd8 100644
--- a/ssl/tls13_client.c
+++ b/ssl/tls13_client.c
@@ -394,6 +394,7 @@
return ssl_hs_error;
}
+ ssl->method->received_flight(ssl);
hs->state = state_certificate_callback;
return ssl_hs_ok;
}
