commit | 64393b57e8734b92a6ba784bcfc02b1aa01e5ff2 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Mon Oct 03 11:26:39 2022 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Oct 03 20:42:56 2022 +0000 |
tree | b40e43f2afac858f26ad8a629060d5a928ddb0fc | |
parent | d8090a173b7e2050a75a0c1a6fcd32b4198069e7 [diff] |
Default SSL_set_enforce_rsa_key_usage to enabled. Update-Note: Clients will now require RSA server certificates used in TLS 1.2 and earlier to include the keyEncipherment or digitalSignature bit. keyEncipherment is required if using RSA key exchange. digitalSignature is required if using ECDHE_RSA key exchange. We already required this for each of ECDSA, TLS 1.3, and servers verifying client certificates, so this just fills in the remaining hole. Chrome has also enforced this for some time with publicly-trusted certificates. For now, the SSL_set_enforce_rsa_key_usage API still exists where we need to turn this off. Fixed: 519 Change-Id: Ia440b00b60a224fa608702439aa120d633d81ddc Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54606 Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: 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:
There are other files in this directory which might be helpful: