|author||David Benjamin <email@example.com>||Wed Oct 28 18:03:21 2015 -0400|
|committer||Adam Langley <firstname.lastname@example.org>||Tue Nov 03 22:50:59 2015 +0000|
Don't bother sampling __func__. Removing the function codes continued to sample __func__ for compatibility with ERR_print_errors_cb, but not ERR_error_string_n. We can just emit OPENSSL_internal for both. ERR_print_errors_cb already has the file and line number available which is strictly more information than the function name. (ERR_error_string_n does not, but we'd already turned that to OPENSSL_internal.) This shaves 100kb from a release build of the bssl tool. In doing so, put an unused function code parameter back into ERR_put_error to align with OpenSSL. We don't need to pass an additional string in anymore, so OpenSSL compatibility with anything which uses ERR_LIB_USER or ERR_get_next_error_library costs nothing. (Not that we need it.) Change-Id: If6af34628319ade4145190b6f30a0d820e00b20d Reviewed-on: https://boringssl-review.googlesource.com/6387 Reviewed-by: Adam Langley <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: