commit | b0251b12956ed8e9e41f7bf0bbb02b337e17ad52 | [log] [tgz] |
---|---|---|
author | David Benjamin <davidben@google.com> | Fri Apr 21 17:56:08 2023 -0400 |
committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue May 23 00:57:56 2023 +0000 |
tree | 27f8a4cfd913439ebb3eb9799e8be195da4db680 | |
parent | 8abcb6fb41cbb29e93ed82048bb3d59bc8e6717f [diff] |
Disable TLS_RSA_WITH_3DES_EDE_CBC_SHA by default 3DES has long been obsolete. It uses a small block size, making it vulnerable to attacks at sufficiently high volumes (see https://sweet32.info/, CVE-2016-6329). On top of this, it is slow even without constant-time protections, making it a DoS risk for server operators. Since the alias "3DES" has existed in OpenSSL for a long time, keep that one working, to reduce the risk of breaking someone who specifically wanted 3DES enabled. Update-Note: This CL disables TLS_RSA_WITH_3DES_EDE_CBC_SHA by default. Specifically, it will not be included unless explicitly listed in the cipher config, as "TLS_RSA_WITH_3DES_EDE_CBC_SHA", its legacy OpenSSL name "DES-CBC3-SHA", or the alias "3DES". To restore it, add one of the above to your cipher config. Bug: 599 Change-Id: Ib94a2f149b3bfa240ef1008b9f3729a9c10368fb Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/59425 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: