Google Git
Sign in
boringssl / boringssl / refs/heads/main
commite8c1dc3679cf211ef9e6323541bd43b5d3e647f6[log] [tgz]
authorDavid Benjamin <davidben@google.com>Sat Sep 20 19:46:42 2025 -0400
committerBoringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com>Sat Sep 20 17:29:02 2025 -0700
tree865bb52cf62a7286548c55ac7e7c8c3b6dd5b0db
parentf875db367c4da75676744cbaeb48a2d20940e510 [diff]
Remove some stale ifdefs from urandom.cc

After 53f09ad241ddf7e37a426a5e3c6dfa6d4dca9706, we use getentropy on
FreeBSD, so the FREEBSD_GETRANDOM check is dead code. urandom.cc can
assume OPENSSL_LINUX is true and include headers accordingly.

We also no longer do the ioctl dance on /dev/urandom in BORINGSSL_FIPS,
so includes for those can be removed.

Change-Id: I394b43ffc05a1ccd1759aac1277e2a2971eddb67
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/82107
Reviewed-by: Adam Langley <agl@google.com>
Commit-Queue: Adam Langley <agl@google.com>
Commit-Queue: David Benjamin <davidben@google.com>
Auto-Submit: David Benjamin <davidben@google.com>
1 file changed
tree: 865bb52cf62a7286548c55ac7e7c8c3b6dd5b0db
  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: