Google Git
Sign in
boringssl / boringssl / 63f42a00cf28e3b5d2c5eddfa06ed16f532bde88
commit63f42a00cf28e3b5d2c5eddfa06ed16f532bde88[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sat Sep 20 19:34:28 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Sun Sep 21 07:56:21 2025 -0700
tree631537a7474028c1c83f2c7afcbbf1cee7c7dabb
parente8c1dc3679cf211ef9e6323541bd43b5d3e647f6 [diff]
Upgrade the opportunistic CRYPTO_sysrand calls to normal ones

We do not believe this is needed anymore. See
go/boringssl-and-os-entropy (internal).

After this change, we still use RDRAND for the seed and the OS for the
personalization string. There's no reason for this now. Rather, this is
meant to be a more easily reverted change. I've left some TODOs to clean
this up, once this sticks.

Update-Note: Builds with BORINGSSL_FIPS will no longer attempt to work
around broken OS entropy with RDRAND. The OS is expected to be
functional.

Bug: 446280903
Change-Id: I60bf9c4c0c1268d76b26301b41097179de453120
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82108
Reviewed-by: Adam Langley <agl@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
Commit-Queue: Adam Langley <agl@google.com>
9 files changed
tree: 631537a7474028c1c83f2c7afcbbf1cee7c7dabb
  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: