commit | 14a077c353b3b750dc3d8de8de9e0ea408c2ba20 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Wed Jul 20 11:16:57 2016 +0200 |
committer | David Benjamin <davidben@google.com> | Wed Jul 20 09:18:11 2016 +0000 |
tree | 2b17db502d56fd39e36c2718835a6ff6d133beb6 | |
parent | 69f40dff83aed9de7e480f658dea65c191bfec7a [diff] |
Revert "Add tests to ensure our ClientHello does not change." This reverts commit 69f40dff83aed9de7e480f658dea65c191bfec7a. I'm not sure why the CQ didn't catch it while the bots didn't, but I'll look into it after the QUIC BoF. Change-Id: Ia187787c86aab082b9cffe0c86c828805dfc212d Reviewed-on: https://boringssl-review.googlesource.com/8870 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: