Require __NR_getrandom to be either available or polyfilled Dating to when getrandom was very new, we wouldn't use getrandom if it wasn't defined in either headers or in the fillin header. Worse, it was defined in headers but not the fillin header, we still wouldn't use it! (Though we had values for all supported architectures, so this is largely moot.) However, after https://boringssl-review.googlesource.com/c/boringssl/+/86487, builds without USE_NR_getrandom broken anyway. (The namespace import was in the wrong file.) Given those were broken anyway, just remove that polyfill. I haven't quite gone as far as to require __NR_getrandom be available in headers, but I suspect we can at this point. (We have a bunch of stale glibc headers around, but IIRC those come from Linux headers rather than glibc headers.) Left a TODO to run a TGP on that. Bug: 446280907 Change-Id: I3b4d4422050e0b5d47f8909d6ad759fcaa144a86 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/89508 Commit-Queue: Lily Chen <chlily@google.com> Reviewed-by: Lily Chen <chlily@google.com> Auto-Submit: David Benjamin <davidben@google.com>
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: