Google Git
Sign in
boringssl / boringssl / 17164fff9c433e482e51d9d3954d8f4815020a91
commit17164fff9c433e482e51d9d3954d8f4815020a91[log] [tgz]
authorLily Chen <chlily@google.com>Fri Jul 18 18:58:11 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 21 08:52:07 2025 -0700
treebb3bd80fd5602efd114060321214e6787271757d
parentdf6e8edbace4f4db02f21f8ae894a4a42d59feb8 [diff]
Pull in Rust toolchain via util/bot/DEPS

Use gclient with the condition 'checkout_rust' to pull in the
update_rust.py script from Chromium. Add a hook to run update_rust.py
to download a copy of the Rust toolchain from GCS.

Because update_rust.py depends upon the tools/clang/scripts/update.py
script, this modifies the condition for boringssl/util/bot/tools/clang
to also fetch the clang script whenever we 'checkout_rust' (but it does
not need to actually run tools/clang/scripts/update.py).

Change-Id: I8e10d99ef6bdad04796eff4a0b98fdf5e0e7c6f0
Bug: 42290446
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80507
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: Lily Chen <chlily@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
2 files changed
tree: bb3bd80fd5602efd114060321214e6787271757d
  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: