kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
bbd43b5e90
boringssl/ssl/test
History
Matt Braithwaite 053931e74e CECPQ1: change from named curve to ciphersuite. 
This is easier to deploy, and more obvious.  This commit reverts a few
pieces of e25775bc, but keeps most of it.

Change-Id: If8d657a4221c665349c06041bb12fffca1527a2c
Reviewed-on: https://boringssl-review.googlesource.com/8061
Reviewed-by: Adam Langley <agl@google.com>
2016-05-26 19:42:35 +00:00
..
runner CECPQ1: change from named curve to ciphersuite. 2016-05-26 19:42:35 +00:00
async_bio.cc Fix DTLS asynchronous write handling. 2015-11-02 23:16:22 +00:00
async_bio.h Fix DTLS asynchronous write handling. 2015-11-02 23:16:22 +00:00
bssl_shim.cc CECPQ1: change from named curve to ciphersuite. 2016-05-26 19:42:35 +00:00
CMakeLists.txt Add malloc test support to unit tests. 2015-05-21 17:59:48 +00:00
packeted_bio.cc
packeted_bio.h Include <sys/time.h> in packeted_bio.h for 'timeval' 2015-12-15 18:11:18 +00:00
README.md Add a README.md for ssl/test. 2016-05-06 17:40:28 +00:00
scoped_types.h
test_config.cc Adding TLS 1.3 constants. 2016-05-25 17:41:36 +00:00
test_config.h Adding TLS 1.3 constants. 2016-05-25 17:41:36 +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.