commit 5c03085cff01cd708ff13479ecd8957bc8184820
author dschinazi <dschinazi@google.com> Thu Jul 11 15:45:53 2019 -0700
committer Copybara-Service <copybara-worker@google.com> Thu Jul 11 15:49:13 2019 -0700
tree 488422daac96fea1f8410e6f3ba18e003a475497
parent 39915f9448d547ac5cf2ca34b4204bf52874935f

Fix replacing connection IDs when initial crypters are in use

When the client uses an initial destination connection ID length different than 8 bytes, we replace that connection ID with a random 8-byte one. However, the initial crypters are still based on that original connection ID. This change makes sure that we initialize the TLS crypters with the right connection ID. This also removes the code that would set the crypters in tls_server_handshaker because that is no longer required now that we've completely removed in-connection version negotiation.

This change also makes sure we correctly check the QuicDispatcher::session_map_ for the replaced connection ID which is required to properly route subsequent long header packets after the first one.

This change is safe without flag protection because it only impacts versions that allow connection IDs of length different than 8, and all those versions are disabled by flags.

gfe-relnote: fix connection ID replacement, protected by quic_enable_v47/48/99
PiperOrigin-RevId: 257697143
Change-Id: Ifc3779e292104656abd72fae79fba8b7604cabe2