| commit | 4f3e8212ea413d0bc271054a12ed581bc742e825 | [log] [tgz] |
|---|---|---|
| author | Matthew Braithwaite <mab@google.com> | Wed Jan 08 16:56:48 2020 -0800 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Mon Feb 10 21:19:46 2020 +0000 |
| tree | 5a4f4ceb6ea809a5f3ea39d593237f3960d8aaed | |
| parent | 7964a1d6768650b8d34da23842f3f14851722afc [diff] |
ssl_test: test early data with split handshakes. This helps to clarify where SSL_set_early_data_enabled() needs to be called: in the shim tests it was being set everywhere, which concealed the fact that the |enable_early_data| bit was not being set by SSL_apply_handback(). Change-Id: I35bfdc6dd43f4fa07ef79eb02e4624b59fcdda5e Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/39385 Commit-Queue: Matt Braithwaite <mab@google.com> 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.
Project links:
There are other files in this directory which might be helpful: