| commit | de2d610a341f5a4b8c222425890537cb84c91400 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Fri Apr 21 17:32:21 2023 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Apr 24 14:01:34 2023 +0000 |
| tree | 83d659b1857df16d7ec7b02b1c5e60541fcc9a64 | |
| parent | b0b1f9dfc583c96d5f91b7f8cdb7efabcf22793b [diff] |
Remove TLS_RSA_WITH_NULL_SHA Per b/31553927, the last use of this is long gone. This cipher has been deprecated since it was (re)-added in 2015, so it's long past time to remove it. Update-Note: TLS_RSA_WITH_NULL_SHA is no longer available. Nothing should be enabling it anymore. Callers using SSL_CTX_set_strict_cipher_list instead of SSL_CTX_set_cipher_list will notice if they're affected very quickly, because the functino will fail if this cipher is referenced. As a deprecated cipher suite, this cipher was already unavailable unless explicitly named, so if your configuration doesn't say "TLS_RSA_WITH_NULL_SHA" or "NULL-SHA", you were not using this cipher. Bug: b:31553927 Change-Id: Id560bb4f9b156be3650d63f4ecf7783fad5ae209 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/59145 Commit-Queue: David Benjamin <davidben@google.com> Reviewed-by: Bob Beck <bbe@google.com> Commit-Queue: Bob Beck <bbe@google.com> Auto-Submit: 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: