Google Git
Sign in
pigweed/third_party/github/google/boringssl/refs/heads/upstream/main
commit
031e739fceefd9fc14ae141a222778b57917cd44
[log] [tgz]
author
Rudolf Polzer <rpolzer@google.com>
Mon Mar 23 01:02:28 2026 -0700
committer
Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>
Mon Mar 23 01:23:51 2026 -0700
tree
8d567ab15a67ce4eeb71feb052e8aeb6c21ac53c
parent
ba3de4d9b41906eb7e50d69edca140ef3cec053a [diff]
Revert "Reapply "Simplify the symbol prefixing macros.""

Chromium is still not ready for it:

https://ci.chromium.org/ui/p/chromium/builders/ci/linux-win-cross-rel/8864/overview

And I honestly have no clue how to fix it.

Bug: 42220000
This reverts commit ba3de4d9b41906eb7e50d69edca140ef3cec053a.

Change-Id: I690b4aa1918848ee86c3b7f87fa181b56a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/91227
Commit-Queue: Xiangfei Ding <xfding@google.com>
Auto-Submit: Rudolf Polzer <rpolzer@google.com>
Commit-Queue: Rudolf Polzer <rpolzer@google.com>
Reviewed-by: Xiangfei Ding <xfding@google.com>
54 files changed
tree: 8d567ab15a67ce4eeb71feb052e8aeb6c21ac53c
  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: