|author||David Benjamin <firstname.lastname@example.org>||Wed Nov 27 16:22:28 2019 -0500|
|committer||CQ bot account: email@example.com <firstname.lastname@example.org>||Mon Dec 02 16:53:32 2019 +0000|
Give ERR_error_string_n a return value for convenience. ERR_error_string_n needs to be called in a separate statement, compared to ERR_error_string(err, NULL), which returns a buffer and is very convenient to use in an expression. This is unfortunate because it is not thread-safe. Give ERR_error_string_n a return value to align. Fixing callers still requires allocating a buffer somewhere, but the rest of the expression can remain relatively unperturbed. Change-Id: I273c9df97f0bb113cdc57cf3896c42195910c67a Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38964 Reviewed-by: Steven Valdez <email@example.com> Commit-Queue: David Benjamin <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: