kris/boringssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
57e929f3c8
boringssl/ssl/test
History
David Benjamin 57e929f3c8 Enable RSA-PSS in TLS 1.2 by default. 
Add a test that RSA-PSS is available in TLS 1.2 by default, both for
signing and verifying. Note that if a custom SSL_PRIVATE_KEY_METHOD is
used and it sets signing preferences, it won't use RSA-PSS if it doesn't
know about it. (See *-Sign-Negotiate-* tests.)

Change-Id: I3776a0c95480188a135795f7ebf31f2b0e0626cc
Reviewed-on: https://boringssl-review.googlesource.com/10723
Commit-Queue: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Reviewed-by: Adam Langley <agl@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2016-08-30 22:50:05 +00:00
..
runner Enable RSA-PSS in TLS 1.2 by default. 2016-08-30 22:50:05 +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 ARRAY_SIZE macro for getting the size of constant arrays. 2016-08-19 19:30:39 +00:00
CMakeLists.txt Add malloc test support to unit tests. 2015-05-21 17:59:48 +00:00
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 Test resuming renewed sessions. 2016-08-18 23:53:19 +00:00
test_config.h Test resuming renewed sessions. 2016-08-18 23:53:19 +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.