Google Git
Sign in
boringssl / boringssl / baaf868e6e8fa45396070cd8d32d196c404d9ff3
commitbaaf868e6e8fa45396070cd8d32d196c404d9ff3[log] [tgz]
authorDavid Benjamin <davidben@google.com>Fri Nov 07 09:53:11 2025 -0500
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Mon Nov 10 17:10:41 2025 -0800
treea7a7d0ced79fc7c32a1eb908fbc8917274a23211
parent0f9f945bf0611922c33b14a543e5935c954eaa65 [diff]
Unwind wait_for_entropy diagnostic function in getrandom code

In non-FIPS config, getrandom's blocking behavior has stuck for many,
many years now. In the FIPS config, we've had the logging for as long,
and as of 63f42a00cf28e3b5d2c5eddfa06ed16f532bde88, will be as visible
as in the FIPS config. That all has stuck without much trouble, so start
cleaning this code up.

This change does not impact whether we block on getrandom because we
already pass a flags of 0 into the actual getrandom call. The
wait_for_entropy machinery was diagnostic-only.

Also inline some helper functions now that we only have one entrypoint
into the OS PRNG.

Bug: 446280903
Change-Id: I3cd735046df9b2c662a695f35f0d1c9c5acecef6
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83728
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: Adam Langley <agl@google.com>
Reviewed-by: Lily Chen <chlily@google.com>
2 files changed
tree: a7a7d0ced79fc7c32a1eb908fbc8917274a23211
  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: