Commit 663ff78e authored by Nick Harper's avatar Nick Harper Committed by Commit Bot

Fix QUIC's GetSSLInfo for 0-RTT TLS handshakes.

https://quiche.googlesource.com/quiche/+/808b6c7b0d8953251b36eeeb34e9974714e9a3af
fixed TlsClientHandshaker::crypto_negotiated_params to return non-empty
params after a 0-RTT handshake is attempted, so the check added in
crrev.com/c/2315435 that the TLS handshake is complete before providing
SSLInfo is no longer needed.

Change-Id: I5d42a58e19e32badea7b1d7d457e3f90dcb39177
Bug: 1122700
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406458
Commit-Queue: Nick Harper <nharper@chromium.org>
Commit-Queue: Renjie Tang <renjietang@chromium.org>
Auto-Submit: Nick Harper <nharper@chromium.org>
Reviewed-by: default avatarRenjie Tang <renjietang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#806379}
parent 0922f052
......@@ -1276,8 +1276,7 @@ bool QuicChromiumClientSession::GetRemoteEndpoint(IPEndPoint* endpoint) {
// we learn about SSL info (sync vs async vs cached).
bool QuicChromiumClientSession::GetSSLInfo(SSLInfo* ssl_info) const {
ssl_info->Reset();
if (!cert_verify_result_ || (connection()->version().UsesTls() &&
!crypto_stream_->one_rtt_keys_available())) {
if (!cert_verify_result_) {
return false;
}
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment