a8ebe2261f
We shouldn't have protocol constraints that are sensitive to whether data is returned synchronously or not. Per https://boringssl-review.googlesource.com/#/c/4112/, the original limitation was to avoid OpenSSL ABI changes. This is no longer a concern. Add tests for the sync and async case. Send the empty records in two batches to ensure the count is reset correctly. Change-Id: I3fee839438527e71adb83d437879bb0d49ca5c07 Reviewed-on: https://boringssl-review.googlesource.com/5040 Reviewed-by: Adam Langley <agl@google.com> |
||
---|---|---|
.. | ||
alert.go | ||
cert.pem | ||
chacha20_poly1305_test.go | ||
chacha20_poly1305.go | ||
channel_id_key.pem | ||
cipher_suites.go | ||
common.go | ||
conn.go | ||
dtls.go | ||
ecdsa_cert.pem | ||
ecdsa_key.pem | ||
handshake_client.go | ||
handshake_messages.go | ||
handshake_server.go | ||
key_agreement.go | ||
key.pem | ||
packet_adapter.go | ||
poly1305.go | ||
prf.go | ||
recordingconn.go | ||
runner.go | ||
test_output.go | ||
ticket.go | ||
tls.go |