Google Git
Sign in
boringssl / boringssl / 6b197714908ea75fe5d354f72ed20f47fa4848c4
commit6b197714908ea75fe5d354f72ed20f47fa4848c4[log] [tgz]
authorMaurice Lam <yukl@google.com>Fri Aug 09 15:00:52 2024 -0700
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Sep 16 19:21:01 2024 +0000
tree58d117425cf50fe7c2ae22ecf2174830dadf5f8b
parentfb61601c5583583140a3b500f8ec9df4829675cf [diff]
Update deny-toml to match new version format

See https://github.com/EmbarkStudios/cargo-deny/pull/611

- Instead of using the template from deny.template.toml, just specify
  the fields that we need to be changed
- Added back comments on bans.allow, but the bssl-sys and bssl-crypto
  crates are not added to the allowlist because they are now allowed
  with `licenses.allow = ["ISC"]`.

Change-Id: I9e693780d902671444bf90b4d158d6e099e87ccb
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/70147
Reviewed-by: Bob Beck <bbe@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
1 file changed
tree: 58d117425cf50fe7c2ae22ecf2174830dadf5f8b
  1. .bcr/
  2. .github/
  3. cmake/
  4. crypto/
  5. decrepit/
  6. docs/
  7. fuzz/
  8. gen/
  9. include/
  10. pki/
  11. rust/
  12. ssl/
  13. third_party/
  14. tool/
  15. util/
  16. .bazelignore
  17. .bazelrc
  18. .clang-format
  19. .gitignore
  20. API-CONVENTIONS.md
  21. BREAKING-CHANGES.md
  22. BUILD.bazel
  23. build.json
  24. BUILDING.md
  25. CMakeLists.txt
  26. codereview.settings
  27. CONTRIBUTING.md
  28. FUZZING.md
  29. go.mod
  30. go.sum
  31. INCORPORATING.md
  32. LICENSE
  33. MODULE.bazel
  34. MODULE.bazel.lock
  35. PORTING.md
  36. PrivacyInfo.xcprivacy
  37. README.md
  38. SANDBOXING.md
  39. 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: