|author||David Benjamin <firstname.lastname@example.org>||Tue Feb 26 22:13:28 2019 -0600|
|committer||Adam Langley <email@example.com>||Tue Mar 05 17:53:16 2019 +0000|
Tell ASan about the OPENSSL_malloc prefix. OpenSSL's BN_mul function had a single-word buffer underflow (see 576129cd72ae054d246221f111aabf42b9c6d76d). We already independently fixed this but, if we hadn't, ASan wouldn't have noticed because of OPENSSL_malloc. ASan has runtime hooks we can call to make it more accurate. Change-Id: Ifc9c3837ece2bc456c5bdc960be707d7b1759904 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35165 Reviewed-by: Adam Langley <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: