kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
867bcba05d
boringssl/ssl/test
History
David Benjamin ee32bea1d3 Fix TLS 1.2 sigalgs fallback logic for ECDSA. 
Also fix up those tests as they were a little confused. It is always the
shim that signs and has a configured certificate in these tests.

BUG=95

Change-Id: I57a6b1bad19986c79cd30aaa6cf3b8ca307ef8b2
Reviewed-on: https://boringssl-review.googlesource.com/10444
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-18 19:41:22 +00:00
..
runner Fix TLS 1.2 sigalgs fallback logic for ECDSA. 2016-08-18 19:41:22 +00:00
async_bio.cc Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
async_bio.h Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
bssl_shim.cc Adding code to send session as PSK Identity. 2016-08-16 20:35:32 +00:00
CMakeLists.txt
packeted_bio.cc Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
packeted_bio.h Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
PORTING.md Fix typo. 2016-08-16 18:05:47 +00:00
README.md Adding PORTING.md for instructions on how to port the test runner 2016-08-16 17:53:28 +00:00
scoped_types.h Revert "Move C++ helpers into |bssl| namespace." 2016-07-12 08:09:33 -07:00
test_config.cc Add SSL_send_fatal_alert. 2016-07-26 22:32:18 +00:00
test_config.h Add SSL_send_fatal_alert. 2016-07-26 22:32:18 +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.