History

David Benjamin a048678cd6 Move some fields from tmp to hs. This releases memory associated with them after the handshake. Note this changes the behavior of \|SSL_get0_certificate_types\| and \|SSL_get_client_CA_list\| slightly. Both functions now return NULL outside of the handshake. But they were already documented to return something undefined when not called at the CertificateRequest. A survey of callers finds none that would care. (Note SSL_get_client_CA_list is used both as a getter for the corresponding server config setter and to report client handshake properties. Only the latter is affected.) It's also pretty difficult to imagine why a caller would wish to query this stuff at any other time, and there are clear benefits to dropping the CA list after the handshake (some servers send ABSURDLY large lists). Change-Id: I3ac3b601ff0cfa601881ce77ae33d99bb5327004 Reviewed-on: https://boringssl-review.googlesource.com/11521 Reviewed-by: Adam Langley <agl@google.com>		2016-10-09 16:47:31 +00:00
..
runner	Test that unknown TLS 1.3 ticket extensions are tolerated.	2016-10-07 21:00:59 +00:00
async_bio.cc	Replace Scoped* heap types with bssl::UniquePtr.	2016-09-01 22:22:54 +00:00
async_bio.h	Replace Scoped* heap types with bssl::UniquePtr.	2016-09-01 22:22:54 +00:00
bssl_shim.cc	Move some fields from tmp to hs.	2016-10-09 16:47:31 +00:00
CMakeLists.txt	Add malloc test support to unit tests.	2015-05-21 17:59:48 +00:00
packeted_bio.cc	Replace Scoped* heap types with bssl::UniquePtr.	2016-09-01 22:22:54 +00:00
packeted_bio.h	Replace Scoped* heap types with bssl::UniquePtr.	2016-09-01 22:22:54 +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	Add tests for very large handshake messages.	2016-09-29 16:31:54 +00:00
test_config.h	Add tests for very large handshake messages.	2016-09-29 16:31:54 +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.