|author||David Benjamin <email@example.com>||Wed Aug 11 18:14:10 2021 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Fri Aug 13 19:18:23 2021 +0000|
Simplify built-in BIOs slightly. The free callbacks can assume their inputs are non-NULL. They're only called from BIOs of the corresponding method, which means the BIO must exist. Also new callbacks that leave everything zero-initialized are no-ops and can be omitted. This removes the weird thing where the built-in free functions were fallible. Although the int return is still necessary for compatibility with external BIOs. Change-Id: I91e2101efc7c77c703cb649df1490bc9f515f0fd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/48846 Reviewed-by: Adam Langley <email@example.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: