Google GitGoogle Git
Sign in
boringssl/boringssl/a539826c55252739b4db155db96adce49fab6259
commit
a539826c55252739b4db155db96adce49fab6259
[log]
author
Rudolf Polzer <rpolzer@google.com>
Mon Mar 23 01:55:46 2026 -0700
committer
Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>
Thu Mar 26 05:34:34 2026 -0700
tree
c99351b89fb3cc539944baf587d00cb583b581d9
parent
b4aca02389a30b11b7acd0ed750fd8c1acf05de0 [diff]
Reapply "Reapply "Simplify the symbol prefixing macros.""

This reverts commit b7d706a3823f3fc9f1ee4706751591f7fe859442.

As Chromium's build system can't handle it, let's not include the
headers always, but still check for BORINGSSL_PREFIX in them; also, the
macros use less case distinctions now.

This reduces the RAM usage of the compiler, but also is generally nicer
in the sense that it now properly autodetects the need to prepend an
underscore rather than relying on Apple vs non-Apple.

It also is part of a potential workaround to use the #pragma
redefine_extname together with precompiled headers.

Bug: 42220000
Change-Id: I773f2820a5852d7f1681383abeb9299c6a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/91247
Reviewed-by: Xiangfei Ding <xfding@google.com>
Commit-Queue: Xiangfei Ding <xfding@google.com>
18 files changed
tree: c99351b89fb3cc539944baf587d00cb583b581d9
  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: