mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-06 10:32:10 +00:00
a19d6ce89c
On Unix, instead of getting random data from `/dev/urandom`, it will get it from the `rand` platform agnostic crate instead. OsRng.fill_bytes on unix will make a syscall to getrandom(2) if available, otherwise it will read from `dev/urandom` after a succesful poll to `dev/random`. Regardless of which way a random data is retrieved, if the entropy pool is not intialized, `fill_bytes` will block until it is intialized. This shouldn't be a problem because it is a one time cost. This CL will also upstream the Windows implementation of the rng device. BUG=b:213149162 TEST=built and presubmits Change-Id: Ic017f11795f8006e0bf2a04eb0478b3a3d336507 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3657812 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Richard Zhang <rizhang@google.com>
9 lines
284 B
Text
9 lines
284 B
Text
# Copyright 2019 The Chromium OS Authors. All rights reserved.
|
|
# Use of this source code is governed by a BSD-style license that can be
|
|
# found in the LICENSE file.
|
|
|
|
@include /usr/share/policy/crosvm/common_device.policy
|
|
|
|
getrandom: 1
|
|
openat: return ENOENT
|
|
prctl: arg0 == PR_SET_NAME
|