| commit | 45dab251f3d000851904af8afaf44851fcc7d182 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@chromium.org> | Fri Dec 04 23:20:43 2015 -0500 |
| committer | Adam Langley <agl@google.com> | Tue Dec 15 21:32:14 2015 +0000 |
| tree | 0eb3d489d2b040581a6cc7d8b635de0d9b753f58 | |
| parent | 8a58933db02f5059202709807562bae0d6633fdb [diff] |
Skip free callbacks on empty CRYPTO_EX_DATAs. Avoids bouncing on the lock, but it doesn't really matter since it's all taking read locks. If we're declaring that callbacks don't get to see every object being created, they shouldn't see every object being destroyed. CRYPTO_dup_ex_data also already had this optimization, though it wasn't documented. BUG=391192 Change-Id: I5b8282335112bca3850a7c0168f8bd7f7d4a2d57 Reviewed-on: https://boringssl-review.googlesource.com/6626 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.
There are other files in this directory which might be helpful: