|author||David Benjamin <firstname.lastname@example.org>||Thu Nov 30 16:41:24 2017 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Thu Nov 30 21:57:17 2017 +0000|
Revert "Support high tag numbers in CBS/CBB." This reverts commit 66801feb175599a6d1eb3845eb7ce0ca84551fb5. This turned out to break a lot more than expected. Hopefully we can reland it soon, but we need to fix up some consumers first. Note due to work that went in later, this is not a trivial revert and should be re-reviewed. Change-Id: I6474b67cce9a8aa03f722f37ad45914b76466bea Reviewed-on: https://boringssl-review.googlesource.com/23644 Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.org> CQ-Verified: CQ bot account: email@example.com <firstname.lastname@example.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: