|author||David Benjamin <email@example.com>||Thu Feb 09 17:45:33 2017 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Fri Feb 17 01:11:14 2017 +0000|
Fix crashes in EVP_CIPHER if cipher_data was not allocated. (Imported from upstream's 1222d273d36277f56c3603a757240c386d55f318.) We'd fixed half of these, but the other half are probably unreachable from code that ran under malloc tests, so we never noticed. It's puzzling why upstream did both this and 166e365ed84dfabec3274baf8a9ef8aa4e677891. It seems you only need one of them. Change-Id: I08074358134180c6661600b66958ba861e7726fb Reviewed-on: https://boringssl-review.googlesource.com/13832 Reviewed-by: David Benjamin <firstname.lastname@example.org> Commit-Queue: David Benjamin <email@example.com> CQ-Verified: CQ bot account: firstname.lastname@example.org <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: