Google Git
Sign in
boringssl / boringssl / 447dc9dcaedb961426ce7f51209fd019b93e6e77
commit447dc9dcaedb961426ce7f51209fd019b93e6e77[log] [tgz]
authorDavid Benjamin <davidben@google.com>Tue Mar 25 15:13:16 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Mar 25 12:28:52 2025 -0700
treedae89bb359f71a154d037a690e1573b0b3d73530
parentdd2c1a3c27a6c4b4813a3054e8cd9c670f272b6f [diff]
Add a missing ifdef to CRYPTO_set_fuzzer_mode call

Although the fuzzers are expected to be used with
FUZZING_BUILD_MODE_UNSAFE_FOR_PRODUCTION, build systems sometimes build
them in a non-fuzzer configuration. Keep the targets working in those
configs.

Change-Id: I351c3f6366ca97cb23144164fd5e49d1fa2286a6
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/78007
Commit-Queue: Bob Beck <bbe@google.com>
Reviewed-by: Bob Beck <bbe@google.com>
1 file changed
tree: dae89bb359f71a154d037a690e1573b0b3d73530
  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: