Google Git
Sign in
boringssl / boringssl.git / refs/tags/0.20241209.0
tagc61d6f279caccd774d8e96b3447efea62d6fb52f
taggerDavid Benjamin <davidben@google.com>Mon Dec 09 11:29:48 2024 -0800
objectb6eec48a579eff1abe70ce6d480a017d6ca3a32c 
0.20241209.0
commitb6eec48a579eff1abe70ce6d480a017d6ca3a32c[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Dec 04 13:48:33 2024 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Dec 09 18:14:40 2024 +0000
treea180042e45f956d0afd5aa28a1032c7cc7effc34
parentbb13a96931dd90d6570fa6151e19ef426d5c641f [diff]
Bump the MODULE.bazel version again

The last one had some GCC warnings that have since been doubly resolved
by both removing the offending build configuration and removing the
offending code.

Change-Id: I7c7921fb85baf5f94d0757182cb2d2531a169fb5
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73967
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
1 file changed
tree: a180042e45f956d0afd5aa28a1032c7cc7effc34
  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. BREAKING-CHANGES.md
  24. BUILD.bazel
  25. build.json
  26. BUILDING.md
  27. CMakeLists.txt
  28. codereview.settings
  29. CONTRIBUTING.md
  30. FUZZING.md
  31. go.mod
  32. go.sum
  33. INCORPORATING.md
  34. LICENSE
  35. MODULE.bazel
  36. MODULE.bazel.lock
  37. PORTING.md
  38. PrivacyInfo.xcprivacy
  39. README.md
  40. SANDBOXING.md
  41. 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: