Google Git
Sign in
boringssl / boringssl / c5fdece07d81b8ec413dfd08edfe1fc8d5f0d832
commitc5fdece07d81b8ec413dfd08edfe1fc8d5f0d832[log] [tgz]
authorRudolf Polzer <rpolzer@google.com>Tue Jan 20 06:12:48 2026 -0800
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 28 00:26:12 2026 -0800
treeabf719bc4b96252b788abfdbd930234e672616f4
parentb523a5f565d8be3055ffe1edf8621fb4e3390956 [diff]
Integrate the new way of C++ symbol prefixing with Bindgen.

Update-Note: bindgen.rs is now created differently; it should though be
optional for downstream builds to take over this change, as prefixing is
and remains optional and unprefixed builds should not be affected.
Nevertheless giving a heads up as there is a chance the changes here
impact a downstream build.

Bug: 42220000
Change-Id: I209dcef63f4581046e1cf5e574aee5476a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87407
Commit-Queue: Rudolf Polzer <rpolzer@google.com>
Reviewed-by: Xiangfei Ding <xfding@google.com>
6 files changed
tree: abf719bc4b96252b788abfdbd930234e672616f4
  1. .bcr/
  2. .github/
  3. bench/
  4. cmake/
  5. crypto/
  6. decrepit/
  7. docs/
  8. fuzz/
  9. gen/
  10. include/
  11. infra/
  12. pki/
  13. rust/
  14. ssl/
  15. third_party/
  16. tool/
  17. util/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-format-ignore
  23. .gitignore
  24. API-CONVENTIONS.md
  25. AUTHORS
  26. BREAKING-CHANGES.md
  27. BUILD.bazel
  28. build.json
  29. BUILDING.md
  30. CMakeLists.txt
  31. codereview.settings
  32. CONTRIBUTING.md
  33. FUZZING.md
  34. go.mod
  35. go.sum
  36. INCORPORATING.md
  37. LICENSE
  38. MODULE.bazel
  39. MODULE.bazel.lock
  40. PORTING.md
  41. PRESUBMIT.py
  42. PrivacyInfo.xcprivacy
  43. README.md
  44. SANDBOXING.md
  45. SECURITY.md
  46. 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: