Google Git
Sign in
boringssl / boringssl.git / df6e8edbace4f4db02f21f8ae894a4a42d59feb8
commitdf6e8edbace4f4db02f21f8ae894a4a42d59feb8[log] [tgz]
authorLily Chen <chlily@google.com>Mon Jul 21 09:08:56 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Jul 21 08:41:26 2025 -0700
tree83c0b4d4061a41d2c1869d128baa86d1cd1eac7f
parent0697c880516634fb1430868d99b4028b5e407465 [diff]
Add a Rust workspace

Define a workspace in rust/ so that bssl-sys and bssl-crypto crates can
be built and tested at once from the rust/ directory:
  cd rust
  cargo build --workspace
  cargo test --workspace

(The --workspace arg is optional since this is a virtual manifest; the
default is the whole workspace.)

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