Google Git
Sign in
boringssl / boringssl / ddb2ca4b48fca9a1c468d83dc513b837331843ac
commitddb2ca4b48fca9a1c468d83dc513b837331843ac[log] [tgz]
authorLily Chen <chlily@google.com>Thu Jul 31 17:08:10 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jul 31 14:22:38 2025 -0700
treeb5b05a6fc4cbc895934fa3e28d71db84abf548c5
parent7d63bd0e024e928e2e61aa88977e9d8064a7ea7c [diff]
Run Rust recipe steps on "win64_rel" builder

Add the Rust recipe steps to the existing "win64_rel" ci and try
builders, and get rid of the "win64_rel_rust" try builder that was just
for testing.

Change-Id: Id0b09aac0b6693b673fa2633c7c4eb793f76c51e
Bug: 42290446
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80987
Commit-Queue: Adam Langley <agl@google.com>
Commit-Queue: Lily Chen <chlily@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Auto-Submit: Lily Chen <chlily@google.com>
3 files changed
tree: b5b05a6fc4cbc895934fa3e28d71db84abf548c5
  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: