Google Git
Sign in
boringssl / boringssl.git / 739613d2e62bd6ab3e7378bf70a5767b50e3c4bf
commit739613d2e62bd6ab3e7378bf70a5767b50e3c4bf[log] [tgz]
authorLily Chen <chlily@google.com>Fri Jul 25 20:05:07 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 28 05:38:50 2025 -0700
treeeea98a287f5f9ee4caf740769f0e062966b84080
parentde186e49bf6492e982fd2b910c75880209528dcd [diff]
Make checkout_rust in util/bot/DEPS also run hooks for clang

In 17164ff, it was asserted that checkout_rust did not need to actually
run util/bot/tools/clang/scripts/update.py, only to pull in the python
script.

This seems incorect after all, as bindgen must be able to find system
header files which it gets from libclang, so for consistency just run
the clang hook so that those header files are in a predictable location.

Change-Id: Ifc577d2847c5da2aa02f7a49b130243e599cb18c
Bug: 42290446
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80787
Reviewed-by: David Benjamin <davidben@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: Lily Chen <chlily@google.com>
1 file changed
tree: eea98a287f5f9ee4caf740769f0e062966b84080
  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: