Google Git
Sign in
boringssl / boringssl / d5440dd2c2c500ac2d3bba4afec47a054b4d99ae
commitd5440dd2c2c500ac2d3bba4afec47a054b4d99ae[log] [tgz]
authorEric Biggers <ebiggers@google.com>Sat Apr 05 00:51:34 2025 +0000
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Apr 04 21:28:51 2025 -0700
treef7dce919d12df74813e9108e638d7bc8a4560e30
parent8d8df26fc54f6e5fb0bf404a76ce973c0413eafc [diff]
Optimize computation of H^2 from H^1 in AES-GCM

Squaring requires fewer multiplications than a generic multiplication,
so take advantage of this when computing H^2 from H^1.  This saves a few
instructions in gcm_init_vpclmulqdq_avx2 and gcm_init_vpclmulqdq_avx512.

Change-Id: I528bd877a53bb2fe5fa03067eda100a81192030f
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78287
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
8 files changed
tree: f7dce919d12df74813e9108e638d7bc8a4560e30
  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: