Google Git
Sign in
boringssl / boringssl / 8225e190c82404c35a41843d5d24778285135e9e
commit8225e190c82404c35a41843d5d24778285135e9e[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Oct 22 13:56:15 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Oct 22 14:08:30 2025 -0700
treed312b385ab26c9f99e769eda159f7eb5af519ef2
parentfdd1e377b619fbf6b140a8be8ab0a9f70c2f35c6 [diff]
Also modernize-use-nullptr the BCM fragments

This was generated with the following command. I skipped /entropy/
because some of those files do not compile as standalone files and
clang-tidy gets upset.

   find crypto/ -name '*.cc.inc' | grep -v /entropy/ | xargs clang-tidy --checks=-*,modernize-use-nullptr -p . --fix
   git-clang-format HEAD~1

(Running the git-clang-format script seems to work better than running
git cl format for me outside a Chromium directory.)

Change-Id: I16f3117119e6ae6ffe0959d730536667b2386635
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83148
Reviewed-by: Lily Chen <chlily@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
49 files changed
tree: d312b385ab26c9f99e769eda159f7eb5af519ef2
  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. PRESUBMIT.py
  40. PrivacyInfo.xcprivacy
  41. README.md
  42. SANDBOXING.md
  43. 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: