700631bdf0
We have a successful TLS 1.3 deployment, in spite of non-compliant middleboxes everywhere, so now let's get this optimization in. It would have been nice to test with this from the beginning, but sadly we forgot about it. Ah well. This shaves 63 bytes off the server's first flight, and then another 21 bytes off the pair of NewSessionTickets. So we'll more easily notice in case of anything catastrophic, tie this behavior to draft 28. Update-Note: This slightly tweaks our draft-28 behavior. Change-Id: I4f176a919bf7181239d6ebb31e7870f12364e0f9 Reviewed-on: https://boringssl-review.googlesource.com/28744 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> |
||
|---|---|---|
| .. | ||
| curve25519 | ||
| ed25519 | ||
| poly1305 | ||
| alert.go | ||
| cert.pem | ||
| chacha20_poly1305_test.go | ||
| chacha20_poly1305.go | ||
| channel_id_key.pem | ||
| cipher_suites.go | ||
| common.go | ||
| conn.go | ||
| deterministic.go | ||
| dtls.go | ||
| ecdsa_p224_cert.pem | ||
| ecdsa_p224_key.pem | ||
| ecdsa_p256_cert.pem | ||
| ecdsa_p256_key.pem | ||
| ecdsa_p384_cert.pem | ||
| ecdsa_p384_key.pem | ||
| ecdsa_p521_cert.pem | ||
| ecdsa_p521_key.pem | ||
| ed25519_cert.pem | ||
| ed25519_key.pem | ||
| fuzzer_mode.json | ||
| handshake_client.go | ||
| handshake_messages.go | ||
| handshake_server.go | ||
| hkdf_test.go | ||
| hkdf.go | ||
| key_agreement.go | ||
| key.pem | ||
| packet_adapter.go | ||
| prf.go | ||
| recordingconn.go | ||
| rsa_1024_cert.pem | ||
| rsa_1024_key.pem | ||
| rsa_chain_cert.pem | ||
| rsa_chain_key.pem | ||
| runner_test.go | ||
| runner.go | ||
| shim_ticket.go | ||
| sign.go | ||
| test_output.go | ||
| ticket.go | ||
| tls.go | ||