Google Git
Sign in
boringssl / boringssl / 770033594cfd4a48ed6045e256826c67aa3d90b6
commit770033594cfd4a48ed6045e256826c67aa3d90b6[log] [tgz]
authorDavid Benjamin <davidben@google.com>Mon Feb 03 16:35:49 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Feb 04 13:14:28 2025 -0800
treeedf6a12a005bb4dccbfcd124861f2094e3ac94ea
parent9a8c72d91959f68fe86291b5d07557a7f1cee906 [diff]
Remove now unnecessary ia32cap_P customizations

Now that we have no assembly references, we only need the customizations
that the wrapper functions in crypto/internal.h consume.

I considered adding little breadcrumbs in comments, but it's very, very
unlikely that they'll come up in some future assembly that we import.
We're not adding new RC4 optimizations, AMD XOP is only going to be
become less relevant, and weakening the constant-time model for
non-hyperthreaded x86 cores is probably the least relevant of all of
these.

Bug: 42290548
Change-Id: I08b9681ac38343889e3687e547c19cd2d4681912
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/75868
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
2 files changed
tree: edf6a12a005bb4dccbfcd124861f2094e3ac94ea
  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: