| commit | d8cd383938102c4533cc2bad78b02bd3a4de6a82 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Thu Aug 29 15:42:43 2024 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Aug 29 23:21:50 2024 +0000 |
| tree | de33fea9612016603ba175aa69d8999386358549 | |
| parent | 6c3a63970fbaea7b4f1db23f3213b0c52586cc6c [diff] |
Allow empty passwords in PEM password callback This aligns with https://github.com/openssl/openssl/pull/6173 from upstream OpenSSL. As part of this, I had to fix PEM_def_callback (which is different in us vs BoringSSL) to use -1 as the error value, not 0. Otherwise errors get misinterpreted as empty strings. As part of this, make sure all the functions being fixed are covered by tests. Fixed: 362788352 Change-Id: I2b5071534c77944d473580fda98d23ae3b54e2d5 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70787 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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:
To file a security issue, use the Chromium process and mention in the report this is for BoringSSL. You can ignore the parts of the process that are specific to Chromium/Chrome.
There are other files in this directory which might be helpful: