You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Steven Valdez 384d0eaf19 Make SSL_get_current_cipher valid during QUIC callbacks. 6 years ago
..
runner Add a per-SSL TLS 1.3 downgrade enforcement option and improve tests. 6 years ago
CMakeLists.txt Support symbol prefixes 6 years ago
PORTING.md Document that malloc tests require a longer timeout. 8 years ago
README.md Adding PORTING.md for instructions on how to port the test runner 8 years ago
async_bio.cc Work around language and compiler bug in memcpy, etc. 7 years ago
async_bio.h Replace Scoped* heap types with bssl::UniquePtr. 8 years ago
bssl_shim.cc Implement TLS 1.3 anti-downgrade signal. 6 years ago
fuzzer.h Remove SSL 3.0 implementation. 6 years ago
fuzzer_tags.h Fuzz SSL_serialize_handoff() and SSL_serialize_handback(). 6 years ago
handshake_util.cc shim: don't clear environment when invoking handshaker. 6 years ago
handshake_util.h shim: perform split handshakes in a separate binary. 6 years ago
handshaker.cc handshaker: kick PRNG when resuming in UNSAFE_DETERMINISTIC_MODE. 6 years ago
packeted_bio.cc Remove support for blocking DTLS timeout handling. 7 years ago
packeted_bio.h Remove support for blocking DTLS timeout handling. 7 years ago
settings_writer.cc shim: move |SettingsWriter| into its own file. 6 years ago
settings_writer.h shim: move |SettingsWriter| into its own file. 6 years ago
test_config.cc Make SSL_get_current_cipher valid during QUIC callbacks. 6 years ago
test_config.h Implement TLS 1.3 anti-downgrade signal. 6 years ago
test_state.cc shim: perform split handshakes in a separate binary. 6 years ago
test_state.h shim: perform split handshakes in a separate binary. 6 years ago

README.md

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 the Config and ProtocolBugs struct 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.