| commit | 7a4aaa4ce715cff03b5eebd68f942258863597f2 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Sep 20 17:58:14 2016 -0400 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 21 17:18:40 2016 +0000 |
| tree | ff1afaff3e11002c67f0f85212b1d8a4ddefd189 | |
| parent | e0ff7670253bf6525bd827125cdf7409f05d32ce [diff] |
Fix TLS 1.3 fuzzer mode in Go. Runner needs to implement fuzzer mode as well so we can record transcripts from it. A bunch of tests were failing: - C and Go disagreed on what fuzzer mode did to TLS 1.3 padding. So we fuzz more code, align Go with C. Fuzzer mode TLS 1.3 still pads but just skips the final AEAD. - The deterministic RNG should be applied per test, not per exchange. It turns out, if your RNG is deterministic, one tends to pick the same session ID over and over which confuses clients. (Resumption is signaled by echoing the session ID.) Now the only failing tests are the ones one would expect to fail. BUG=79 Change-Id: Ica23881a6e726adae71e6767730519214ebcd62a Reviewed-on: https://boringssl-review.googlesource.com/11126 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: