| commit | 2d0808094ae07c354c5457a0ab5ee243a5793fcc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Jun 30 17:15:43 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Jun 30 14:40:49 2025 -0700 |
| tree | 796f5ca9d2a85347b65a0ca4d79b51ca8503c65e | |
| parent | e5920933352e9c49a2f899026114882afb89bfff [diff] |
Remove the SHA-1 default for PSS with EVP_PKEY Nothing seems to rely on this for PSS, which is good as SHA-1 is not safe for use with PSS. The OAEP default is sadly harder to remove. Node depends on it. However SHA-1 in OAEP is less pressing, so this is probably okay to leave alone for now, though not ideal. Update-Note: PSS with the EVP APIs will no longer work without an explicit choice of hash function. Previously the default was SHA-1, a broken hash algorithm. Callers can restore the use of SHA-1 with EVP_PKEY_CTX_set_signature_md. Bug: 389733571 Change-Id: I8844764989d170d4b0b435367f0b15d5b892d96d Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80008 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Adam Langley <agl@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@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: