boringssl/ssl/test/runner
Steven Valdez 2a0707210a Prevent Channel ID and Custom Extensions on 0-RTT.
Channel ID is incompatible with 0-RTT, so we gracefully decline 0-RTT
as a server and forbid their combination as a client. We'll keep this
logic around until Channel ID is removed.

Channel ID will be replaced by tokbind which currently uses custom
extensions. Those will need additional logic to work with 0-RTT.
This is not implemented yet so, for now, fail if both are ever
configured together at all. A later change will allow the two to
combine.

BUG=183

Change-Id: I46c5ba883ccd47930349691fb08074a1fab13d5f
Reviewed-on: https://boringssl-review.googlesource.com/14370
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2017-03-26 18:13:57 +00:00
..
curve25519
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
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 Prevent Channel ID and Custom Extensions on 0-RTT. 2017-03-26 18:13:57 +00:00
shim_ticket.go
sign.go
test_output.go
ticket.go
tls.go