|author||David Benjamin <email@example.com>||Thu Apr 18 13:42:30 2019 -0500|
|committer||CQ bot account: firstname.lastname@example.org <email@example.com>||Thu Apr 18 18:58:03 2019 +0000|
Make X509_verify_cert_error_string thread-safe. If the error is unknown, we should not return a static buffer. See also c0a445a9f279d8c4a519b58e52a50112f2341070 from upstream. Change-Id: I23e1a3b9e29b34ab3dff41b8a58155683bbb9bd2 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/35684 Commit-Queue: David Benjamin <firstname.lastname@example.org> Commit-Queue: Adam Langley <email@example.com> Reviewed-by: Adam Langley <firstname.lastname@example.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: