History

David Benjamin ed84291188 Revert "Pack encrypted handshake messages together." This reverts commit `75d43b5785`. Chatting with EKR, there is some reason to believe that doing this might cause more middlebox issues. Since we're still in the middle of working towards viable deployment in the first place, revert this. We can experiment with this later. I should have arranged for this to be controlled more carefully anyway. Change-Id: I0c8bf578f9d7364e913894e1bf3c2b8123dfd770 Reviewed-on: https://boringssl-review.googlesource.com/22204 Reviewed-by: Steven Valdez <svaldez@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>		2017-10-27 14:36:37 +00:00
..
runner	Revert "Pack encrypted handshake messages together."	2017-10-27 14:36:37 +00:00
async_bio.cc	Work around language and compiler bug in memcpy, etc.	2016-12-21 20:34:47 +00:00
async_bio.h	Replace Scoped* heap types with bssl::UniquePtr.	2016-09-01 22:22:54 +00:00
bssl_shim.cc	Check early ALPN before offering 0-RTT.	2017-10-25 03:31:56 +00:00
CMakeLists.txt
fuzzer_tags.h	Share all of fuzz/{client,server}.cc into fuzzer.h.	2017-09-07 22:14:12 +00:00
fuzzer.h	Add DTLS fuzzers.	2017-09-07 22:26:50 +00:00
packeted_bio.cc	Remove support for blocking DTLS timeout handling.	2017-03-01 19:59:28 +00:00
packeted_bio.h	Remove support for blocking DTLS timeout handling.	2017-03-01 19:59:28 +00:00
PORTING.md	Document that malloc tests require a longer timeout.	2016-09-30 19:13:05 +00:00
README.md	Adding PORTING.md for instructions on how to port the test runner	2016-08-16 17:53:28 +00:00
test_config.cc	Check early ALPN before offering 0-RTT.	2017-10-25 03:31:56 +00:00
test_config.h	Check early ALPN before offering 0-RTT.	2017-10-25 03:31:56 +00:00

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.