Google Git
Sign in
boringssl / boringssl / e94d0a93a7df1eb2df7b868e7c231d9fc645fe17
commite94d0a93a7df1eb2df7b868e7c231d9fc645fe17[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Mar 12 11:39:04 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Mar 12 15:30:44 2025 -0700
tree9bc82dad4b634d09bd20a15e6face1d7c4f8eb15
parentb483b0c4358c19d325b19a0fb8ce8524186d77a9 [diff]
Move some exponentation functions out of the FIPS module

BN_exp is never used in cryptography.

We never call BN_mod_exp from the library and instead call the specific
implementations directly.

We never call BN_mod_exp_mont_word. Looks like this was originally added
for optimized small generator operations in Diffie-Hellman, but we
dropped the optimizations. We consider (non-EC) Diffie-Hellman to be a
legacy algorithm.

BN_mod_exp2_mont is used in DSA, but we dropped the optimizations
(non-EC) DSA is also a legacy algorithm and DSA is not in the FIPS
module.

Change-Id: I1cf2975a834f1da12f4e7623339739de151a3e1e
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77447
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
8 files changed
tree: 9bc82dad4b634d09bd20a15e6face1d7c4f8eb15
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. infra/
  11. pki/
  12. rust/
  13. ssl/
  14. third_party/
  15. tool/
  16. util/
  17. .bazelignore
  18. .bazelrc
  19. .bazelversion
  20. .clang-format
  21. .gitignore
  22. API-CONVENTIONS.md
  23. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. STYLE.md
README.md

BoringSSL

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: