| commit | 5a3a1e22ceef5e9dbb9577ee2df3a766488ab4bc | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Wed Mar 26 12:47:28 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 26 10:20:05 2025 -0700 |
| tree | f860f41fdf149d1ef8712c0249658a56442aa0b6 | |
| parent | 5b6b14d9966383ae5240f659fd3ed2e7e9e09a91 [diff] |
Revert "Remove Karatsuba multiplication in BIGNUM" This reverts commit 89eb6ddbf52887631ca45ad2242862515cd698ab. Sadly, exactfloat, a decidedly non-cryptographic use case, uses BN_mul with large enough inputs that Karatsuba is actually a load-bearing optimization. (They're also why we need to support allocating giant BIGNUMs.) This CL just reverts the change for now. We should revise thresholds and rearrange code so that this code is not reachable from any of the cryptographic code. From there, we can revert the work to make it constant-time, which will be better from exactfloat and also remove some complexity. Bug: 406497222 Change-Id: I08b6d12e19c2a6ae741ac490d81cc534ba260145 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78047 Commit-Queue: Bob Beck <bbe@google.com> Reviewed-by: Bob Beck <bbe@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: