| commit | 45610f9afba986cd86d6107c914cf3a5f0663772 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Sat Sep 14 14:11:38 2019 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Sep 30 18:05:44 2019 +0000 |
| tree | 8df7cff2b2da0ac0c673b761ff8cc0b0d9406651 | |
| parent | 6784dc718cee1d7c9d1326ef7857e096c2bde570 [diff] |
Assert that BN_CTX_end is actually called. If a function forgets to BN_CTX_end, everything will work but we'll use more memory than intended. Catch such errors by asserting in BN_CTX_free. Update-Note: BN_CTX is exposed publicly. Some callers may have been using it wrong and trip this assert. If so, add the missing BN_CTX_end calls. Change-Id: I9c38431376a256e5176fd295c0114a10a7f588bd Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/37787 Reviewed-by: Adam Langley <agl@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.
Project links:
There are other files in this directory which might be helpful: