Google Git
Sign in
boringssl / boringssl / 0ea8c5998cc59ce0212766f280ed23b87f93ce47
commit0ea8c5998cc59ce0212766f280ed23b87f93ce47[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Nov 12 11:03:30 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 12 08:52:59 2025 -0800
treece50cf80f4d392ff1bb056e58ad846b8cd02fdbd
parent4c2a6a5467e4abea270877740b5975cac772802d [diff]
Update NDK on CI to r29

This should silence the CMake deprecation warning, and also update to an
NDK with a new enough LLD for the linker-script-based delocate.

Change-Id: Iae8fcbf9468aa62736dd4b498a6224cdb3eae130
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/84087
Commit-Queue: Lily Chen <chlily@google.com>
Reviewed-by: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: ce50cf80f4d392ff1bb056e58ad846b8cd02fdbd
  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. .clang-format-ignore
  22. .gitignore
  23. API-CONVENTIONS.md
  24. AUTHORS
  25. BREAKING-CHANGES.md
  26. BUILD.bazel
  27. build.json
  28. BUILDING.md
  29. CMakeLists.txt
  30. codereview.settings
  31. CONTRIBUTING.md
  32. FUZZING.md
  33. go.mod
  34. go.sum
  35. INCORPORATING.md
  36. LICENSE
  37. MODULE.bazel
  38. MODULE.bazel.lock
  39. PORTING.md
  40. PRESUBMIT.py
  41. PrivacyInfo.xcprivacy
  42. README.md
  43. SANDBOXING.md
  44. 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: