| commit | 100e21271e7e02ef4b87fa519d832b882971c152 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Mon Dec 25 23:38:05 2023 -0500 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 24 00:08:30 2024 +0000 |
| tree | aa7848cf34eb1f8b173fc9f0b082b9eebb48c85c | |
| parent | 3d9e5a355b1ce8518aefce2df00dfab3fe63c379 [diff] |
Stop processing the Netscape cert type extension This is an old predecessor to the extended key usage extension, with no tests. Other implementations, such as Chromium's certificate verifier or Go's already do not process it. This doesn't remove the parser for the extension, or the config-based machinery. Folks who want to manually process the extension or construct it can continue to do so. Update-Note: Certificates with a critical Netscape cert type extension will now be rejected by the certificate verifier, matching the behavior of the Chromium verifier. Non-critical extensions will continue to work fine. They will instead be ignored. Change-Id: I5889fb48f00d8dc081fe784d5f1d73d1b884ca5c Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65209 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: