Google Git
Sign in
boringssl / boringssl / 7c25e7308c3c322c2a0916ad03796945eb5b88eb
commit7c25e7308c3c322c2a0916ad03796945eb5b88eb[log] [tgz]
authorDavid Benjamin <davidben@google.com>Thu Mar 20 17:27:24 2025 +0700
committerDavid Benjamin <davidben@google.com>Thu Mar 20 05:25:29 2025 -0700
tree931bcbfc453b25919b119c0efa719dd1537b81fc
parent03d0f706825cb19773d5b37dcbed402b7508c925 [diff]
Fix fuzzer build on Windows

https://ci.chromium.org/ui/p/chromium/builders/try/win-libfuzzer-asan-rel/2118578/overview

Change-Id: Id195253592610d849a3c4218295a62c320574ed4
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/77867
Reviewed-by: Bob Beck <bbe@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: 931bcbfc453b25919b119c0efa719dd1537b81fc
  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: