|author||David Benjamin <email@example.com>||Mon Mar 20 17:16:19 2017 -0400|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Tue Mar 21 18:10:51 2017 +0000|
Fix potential memory leak in ASN1_TIME_to_generalizedtime() If ret is allocated, it may be leaked on error. (Imported from upstream's cdfb7809b6a365a0a7874afd8f8778c5c572f267 and ffcdb0e6efb6fb7033b2cd29e8cca2e2fe355c14.) Change-Id: I50ed9ad072cf80461d9527d0834b596a8c32e3d3 Reviewed-on: https://boringssl-review.googlesource.com/14315 Reviewed-by: Steven Valdez <firstname.lastname@example.org> Commit-Queue: Steven Valdez <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: