75d43b5785
This does not affect TLS 1.2 (beyond Channel ID or NPN) but, in TLS 1.3, we send several encrypted handshake messages in a row. For the server, this means 66 wasted bytes in TLS 1.3. Since OpenSSL has otherwise used one record per message since the beginning and unencrypted overhead is less interesting, leave that behavior as-is for the time being. (This isn't the most pressing use of the breakage budget.) But TLS 1.3 is new, so get this tight from the start. Change-Id: I64dbd590a62469d296e1f10673c14bcd0c62919a Reviewed-on: https://boringssl-review.googlesource.com/22068 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Steven Valdez <svaldez@google.com> |
||
---|---|---|
.. | ||
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 |