Google Git
Sign in
boringssl / boringssl / 87dff582e4f49bacdd6526f807d2a7cd52b17831
commit87dff582e4f49bacdd6526f807d2a7cd52b17831[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Oct 08 13:10:43 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Oct 08 16:38:44 2025 -0700
tree9a46556f6261cb5f81128407950246c077ac6527
parent08a77f3d88475b092c365d12576de078a54a6d91 [diff]
Unwind <openssl/bcm_public.h>

This was envisioned as part of a (very long) path to manage some version
skew, but we're no longer planning to support this version skew.

bcm_interface.h is still useful so that the BCM calling convention can
handle FIPS nuisances like the FIPS service indicator, and to keep BCM's
functions from peeking out of the public API. But headers, plain
structs, and constants are okay.

Change-Id: I95f26f587929bbf380281cda8aa63f1557159a1c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82687
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
17 files changed
tree: 9a46556f6261cb5f81128407950246c077ac6527
  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. .gitignore
  22. API-CONVENTIONS.md
  23. AUTHORS
  24. BREAKING-CHANGES.md
  25. BUILD.bazel
  26. build.json
  27. BUILDING.md
  28. CMakeLists.txt
  29. codereview.settings
  30. CONTRIBUTING.md
  31. FUZZING.md
  32. go.mod
  33. go.sum
  34. INCORPORATING.md
  35. LICENSE
  36. MODULE.bazel
  37. MODULE.bazel.lock
  38. PORTING.md
  39. PrivacyInfo.xcprivacy
  40. README.md
  41. SANDBOXING.md
  42. 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: