Google Git
Sign in
boringssl / boringssl / 599a3d54c093ce392fcd6a3b5c4b81911c623d08
commit599a3d54c093ce392fcd6a3b5c4b81911c623d08[log] [tgz]
authorRudolf Polzer <rpolzer@google.com>Mon Jan 19 03:18:08 2026 -0800
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Jan 21 04:50:38 2026 -0800
tree173d78f3f730450404e7462dd5c53787969a20d6
parent68a7d7324acc30871604e37122e2e1e11aa6eda3 [diff]
Fix asm symbol prefixing includes:

- For nasm, include the BoringSSL prefix directly in the macros (which
  in this preprocessor is possible, unlike C's).
- For nasm, put the _ only on x86-64, not on x86.
- Include p_thread_callback_boringssl as an asm symbol, as it's used in
  an asm-like way and must be prefixed.

Bug: 42220000
Change-Id: I13f950275b9128ebc29ce5ce8d9ad9f26a6a6964
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/87387
Reviewed-by: Xiangfei Ding <xfding@google.com>
Auto-Submit: Rudolf Polzer <rpolzer@google.com>
Commit-Queue: Rudolf Polzer <rpolzer@google.com>
7 files changed
tree: 173d78f3f730450404e7462dd5c53787969a20d6
  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. 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: