| commit | c0e15d1d9d99bf5f603413e30ea5b6abd87ef9c1 | [log] [tgz] |
|---|---|---|
| author | Martin Kreichgauer <martinkr@google.com> | Fri Aug 18 14:24:36 2017 -0700 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Wed Sep 06 19:22:46 2017 +0000 |
| tree | b11349d143f8b0acf428fe9fb51ca505a1526309 | |
| parent | a23b68f564fc412bd23d3f46b15a2bcd4825e480 [diff] |
Zero memory in |OPENSSL_free|. Allocations by |OPENSSL_malloc| are prefixed with their length. |OPENSSL_free| zeros the allocation before calling free(), eliminating the need for a separate call to |OPENSSL_cleanse| for sensitive data. This change will be followed up by the cleanup in https://boringssl-review.googlesource.com/c/boringssl/+/19824. Change-Id: Ie272f07e9248d7d78af9aea81dacec0fdb7484c4 Reviewed-on: https://boringssl-review.googlesource.com/19544 Reviewed-by: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Martin Kreichgauer <martinkr@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.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: