swtpm: Check for good entropy source in chroot environment #907
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Very old OpenSSL versions (e.g., 1.1.0i) are using /dev/urandom to get entropy while newer ones are using the getrandom syscall that does not need the device file. In some environments access to the created /dev/urandom device file may not work (EACCESS; chroot test case) and then OpenSSL will start failing operations that depend on good entropy. Therefore, check the status of the random number generator after chroot. Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
stefanberger
force-pushed
the
master.next
branch
from
ab99ae0 to
abb4f18
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Very old OpenSSL versions (e.g., 1.1.0i) are using /dev/urandom to get entropy while newer ones are using the getrandom syscall that does not need the device file. In some environments access to the created /dev/urandom device file may not work (EACCESS; chroot test case) and then OpenSSL will start failing operations that depend on good entropy. Therefore, check the status of the random number generator after chroot.