17b3083373
In TLS 1.2, resumption's benefits are more-or-less subsumed by False Start. TLS 1.2 resumption lifetime is bounded by how much traffic we are willing to encrypt without fresh key material, so the lifetime is short. Renewal uses the same key, so we do not allow it to increase lifetimes. In TLS 1.3, resumption unlocks 0-RTT. We do not implement psk_ke, so resumption incorporates fresh key material into both encrypted traffic (except for early data) and renewed tickets. Thus we are both more willing to and more interested in longer lifetimes for tickets. Renewal is also not useless. Thus in TLS 1.3, lifetime is bound separately by the lifetime of a given secret as a psk_dhe_ke authenticator and the lifetime of the online signature which authenticated the initial handshake. This change maintains two lifetimes on an SSL_SESSION: timeout which is the renewable lifetime of this ticket, and auth_timeout which is the non-renewable cliff. It also separates the TLS 1.2 and TLS 1.3 timeouts. The old session timeout defaults and configuration apply to TLS 1.3, and we define new ones for TLS 1.3. Finally, this makes us honor the NewSessionTicket timeout in TLS 1.3. It's no longer a "hint" in 1.3 and there's probably value in avoiding known-useless 0-RTT offers. BUG=120 Change-Id: Iac46d56e5a6a377d8b88b8fa31f492d534cb1b85 Reviewed-on: https://boringssl-review.googlesource.com/13503 Reviewed-by: Adam Langley <agl@google.com> |
||
|---|---|---|
| .. | ||
| runner | ||
| async_bio.cc | ||
| async_bio.h | ||
| bssl_shim.cc | ||
| CMakeLists.txt | ||
| packeted_bio.cc | ||
| packeted_bio.h | ||
| PORTING.md | ||
| README.md | ||
| test_config.cc | ||
| test_config.h | ||
BoringSSL SSL Tests
This directory contains BoringSSL's protocol-level test suite.
Testing a TLS implementation can be difficult. We need to produce invalid but sufficiently correct handshakes to get our implementation close to its edge cases. TLS's cryptographic steps mean we cannot use a transcript and effectively need a TLS implementation on the other end. But we do not wish to litter BoringSSL with options for bugs to test against.
Instead, we use a fork of the Go crypto/tls package, heavily patched with
configurable bugs. This code, along with a test suite and harness written in Go,
lives in the runner directory. The harness runs BoringSSL via a C/C++ shim
binary which lives in this directory. All communication with the shim binary
occurs with command-line flags, sockets, and standard I/O.
This strategy also ensures we always test against a second implementation. All features should be implemented twice, once in C for BoringSSL and once in Go for testing. If possible, the Go code should be suitable for potentially upstreaming. However, sometimes test code has different needs. For example, our test DTLS code enforces strict ordering on sequence numbers and has controlled packet drop simulation.
To run the tests manually, run go test from the runner directory. It takes
command-line flags found at the top of runner/runner.go. The -help option
also works after using go test -c to make a runner.test binary first.
If adding a new test, these files may be a good starting point:
runner/runner.go: the test harness and all the individual tests.runner/common.go: contains theConfigandProtocolBugsstruct which control the Go TLS implementation's behavior.test_config.h,test_config.cc: the command-line flags which control the shim's behavior.bssl_shim.cc: the shim binary itself.
For porting the test suite to a different implementation see PORTING.md.