| commit | dbad745811195c00b729efd0ee0a09b7d9fce1d2 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Feb 20 15:06:57 2024 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Mar 11 23:26:13 2024 +0000 |
| tree | 8e23997ad589cb02fa009b8e2757d1fd2d506489 | |
| parent | 5ee4e9512e9a99f97c4a3fad397034028b3457c2 [diff] |
Add ERR_lib_symbol_name and ERR_reason_symbol_name CPython needs this operation. See https://github.com/openssl/openssl/issues/19848 and https://discuss.python.org/t/error-tables-in-the-ssl-module/25431 for details. In principle, our functions already return the symbol names. The differences are: - Our library strings say "common libcrypto routines" instead of "CRYPTO". - The global reason codes say "internal error" instead of "INTERNAL_ERROR". (We should consider changing this.) - The library forwarding reason codes (ERR_R_BN_LIB) say the library string instead of "BN_LIB". (We should consider changing this.) - errnos report strerror - Unknown errors return "unknown error" because we've found that projects tend to crash when these APIs return NULL. The new APIs consistently return the symbol name, when available. If unavailable (ERR_LIB_SYS's errno reasons), it returns NULL because I assume callers would rather be able to handle that case themselves. Hopefully this will not be as common so callers can take on this one. Change-Id: Idd9e4b1cb5a4f64513310d8066d6bf3970722c23 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/66807 Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: David Benjamin <davidben@google.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.
Project links:
There are other files in this directory which might be helpful: