|author||David Benjamin <email@example.com>||Thu Mar 14 19:25:41 2019 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Mon Mar 18 19:18:31 2019 +0000|
Rewrite BN_CTX. While allocating near INT_MAX BIGNUMs or stack frames would never happen, we should properly handle overflow here. Rewrite it to just be a STACK_OF(BIGNUM) plus a stack of indices. Also simplify the error-handling. If we make the errors truly sticky (rather than just sticky per frame), we don't need to keep track of err_stack and friends. Thanks to mlbrown for reporting the integer overflows in the original implementation. Bug: chromium:942269 Change-Id: Ie9c9baea3eeb82d65d88b1cb1388861f5cd84fe5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35328 Commit-Queue: Adam Langley <firstname.lastname@example.org> 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: