079b394c49
On the client we'll leave it off by default until the change has made it through Chrome's release process. For TLS 1.3, there is no existing breakage risk, so always do it. This saves us the trouble of having to manually turn it on in servers. See [0] for a data point of someone getting it wrong. [0] https://hg.mozilla.org/projects/nss/rev/9dbc21b1c3cc Change-Id: I74daad9e7efd2040e9d66d72d558b31f145e6c4c Reviewed-on: https://boringssl-review.googlesource.com/11680 Reviewed-by: Adam Langley <agl@google.com> |
||
---|---|---|
.. | ||
curve25519 | ||
newhope | ||
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_p256_cert.pem | ||
ecdsa_p256_key.pem | ||
ecdsa_p384_cert.pem | ||
ecdsa_p384_key.pem | ||
ecdsa_p521_cert.pem | ||
ecdsa_p521_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 | ||
runner_test.go | ||
runner.go | ||
sign.go | ||
test_output.go | ||
ticket.go | ||
tls.go |