Use CRYPTO_pre_sandbox_init from BoringSSL.
This uses a BoringSSL abstraction for reading things like /proc/cpuinfo or opening /dev/urandom ahead of time. Rather than using RAND_set_urandom_fd to pass the //base copy of /dev/urandom to BoringSSL, we ask BoringSSL to open it internally (which it may not need at all if the system supports getrandom). This also means we may later be able to have base::RandBytes call into BoringSSL and pick up getrandom, etc., support. See https://boringssl.googlesource.com/boringssl/+/HEAD/SANDBOXING.md Change-Id: I7c9160fb76a5f20a360974408605f2f8438ae177 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2203227Reviewed-by:Matthew Denton <mpdenton@chromium.org> Reviewed-by:
Ken Rockot <rockot@google.com> Commit-Queue: David Benjamin <davidben@chromium.org> Cr-Commit-Position: refs/heads/master@{#769948}
Showing
Please register or sign in to comment