| commit | 82261be65c368bbcf1428f90163e0eac26d57642 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Jul 07 14:32:50 2016 -0700 |
| committer | David Benjamin <davidben@google.com> | Thu Jul 07 23:46:17 2016 +0000 |
| tree | 92e327637e113743d6ddf20e56e71dcc3ccaded4 | |
| parent | b41d2e41b1b24b914c194a00d51df0e7b6c4b8fd [diff] |
Improve CCS/Handshake synchronization tests. Test with and without PackHandshakeFlight enabled to cover when the early post-CCS fragment will get packed into one of the pre-CCS handshake records. Also test the resumption cases too to cover more state transitions. The various CCS-related tests (since CCS is kind of a mess) are pulled into their own group. Change-Id: I6384f2fb28d9885cd2b06d59e765e080e3822d8a Reviewed-on: https://boringssl-review.googlesource.com/8661 Reviewed-by: David Benjamin <davidben@google.com>
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: