Google Git
Sign in
boringssl / boringssl.git / 027492ce55497b9846cb5457dcdf9930538498d1
commit027492ce55497b9846cb5457dcdf9930538498d1[log] [tgz]
authorDavid Benjamin <davidben@google.com>Wed Oct 29 10:12:21 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Nov 05 15:39:51 2025 -0800
treebf5349356f00cbedd77cd2b3ab59f1c669d532a8
parent91a66a59b6c1435120ff83e245d7719411294386 [diff]
Remove ro.boringcrypto.hwrand toggle on Android

After Linux 5.6, the GRND_RANDOM flag is a no-op. Also after the
prng_seeder on Android, we don't run the codepath that looks at this
flag anyway.

This lets us fold CRYPTO_sysrand_for_seed and CRYPTO_sysrand back into
one function. That, in turn, avoids goofiness over whether to use
CRYPTO_sysrand or CRYPTO_sysrand_for_seed when we cleanup the remnants
of the RDRAND workaround.

Bug: 446280903
Change-Id: Ifbf78bf70f7109607a4800fa4409a840b7965af0
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83428
Auto-Submit: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
12 files changed
tree: bf5349356f00cbedd77cd2b3ab59f1c669d532a8
  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. .clang-format-ignore
  22. .gitignore
  23. API-CONVENTIONS.md
  24. AUTHORS
  25. BREAKING-CHANGES.md
  26. BUILD.bazel
  27. build.json
  28. BUILDING.md
  29. CMakeLists.txt
  30. codereview.settings
  31. CONTRIBUTING.md
  32. FUZZING.md
  33. go.mod
  34. go.sum
  35. INCORPORATING.md
  36. LICENSE
  37. MODULE.bazel
  38. MODULE.bazel.lock
  39. PORTING.md
  40. PRESUBMIT.py
  41. PrivacyInfo.xcprivacy
  42. README.md
  43. SANDBOXING.md
  44. 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: