| commit | d3f41b1f8bdbcb7c18937ee3b60ecb972fbebaf7 | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Oct 21 18:27:57 2025 -0400 |
| committer | Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 21 16:24:58 2025 -0700 |
| tree | 3632e4b6b40ea3ab4a7da0a6b72b8d11d0615e66 | |
| parent | 8cb07f5017c1f3826fe891f7fe1b84395066d98c [diff] |
Apply modernize-use-nullptr fixes in all .cc files Just fix these all in one go. This was done with the following command: find crypto/ decrepit/ pki/ ssl/ -name '*.cc' | xargs clang-tidy --checks=-*,modernize-use-nullptr -p . --fix Then I ran git cl format, after wrestling with CHROMIUM_BUILDTOOLS_PATH a bit to get it to run. (That mode seems to be broken? I had to add a symlink somewhere.) Change-Id: I471b12f3f59cabfddc5b3b979b6353f08fdf0ec3 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83067 Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Lily Chen <chlily@google.com>
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: