Google Git
Sign in
boringssl / boringssl / 84ffc174ccfbc74af81e5ee7c51334ecc957c68d
commit84ffc174ccfbc74af81e5ee7c51334ecc957c68d[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue May 06 22:45:36 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed May 07 10:22:29 2025 -0700
treef247ac11fd21a52abb21dc9e56ee2e14d4b40f4e
parent50f67a3ad11cc34e783086cc8831b89077d5a175 [diff]
Test non-NEON codepaths with a OPENSSL_NO_STATIC_NEON_FOR_TESTING

This removes the blocker on updating the NDK. The actual test-only build
flag isn't amazing, but it's much simpler than assembling a custom Arm
toolchain. Time spent on that is probably better spent on removing the
assembly in question, as it'll only be less and less relevant.

Note that, although this CL changes code and main.star at the same
time, LUCI is not capable of updating them atomically, so we'll still
run the old main.star against the new code.

Fixed: 42290318
Change-Id: Ia08350284d47cd5767aa6fd15a2e44443b90ae18
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79148
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
4 files changed
tree: f247ac11fd21a52abb21dc9e56ee2e14d4b40f4e
  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: