| commit | b5e4a225e4102157ebf5c53ccdcb749ebe914797 | [log] [tgz] |
|---|---|---|
| author | Chris Kennelly <ckennelly@google.com> | Mon Sep 10 11:47:15 2018 -0400 |
| committer | Adam Langley <agl@google.com> | Mon Sep 17 21:02:59 2018 +0000 |
| tree | 35cb238cad5e7cd348ee8a6c73d0945ed478c175 | |
| parent | d1673c2191034a65b38c5553a19572f26b122703 [diff] |
Use sdallocx, if available, when deallocating. Providing a size hint to the allocator is substantially faster, especially as we already know/need the size for OPENSSL_cleanse. We provide a weak symbol that falls back to free when a malloc with sdallocx is not statically linked with BoringSSL. Alternatives considered: * Use dlsym(): This is prone to fail on statically linked binaries without symbols. Additionally, the extra indirection adds call overhead above and beyond the linker resolved technique we're using. * Use CMake rules to identify whether sdallocx is available: Once the library is built, we may link against a variety of malloc implementations (not all of which may have sdallocx), so we need to have a fallback when the symbol is unavailable. Change-Id: I3a78e88fac5b6e5d4712aa0347d2ba6b43046e07 Reviewed-on: https://boringssl-review.googlesource.com/31784 Reviewed-by: Chris Kennelly <ckennelly@google.com> 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: