Closed ppmag closed 3 years ago
There a few possible solutions:
aws_nitro_enclaves_library_seed_entropy
explicitly during application start, and on a timer afterwards. rngd
or similar can help with this.random.trust_cpu=on
in the kernel commandline (only works on Linux kernels > 4.19).It might be possible to integrate calls to generate entropy and seed entropy into the provided init process of the enclave, but might not be the best option.
Thank you very much,
first option (aws_nitro_enclaves_library_seed_entropy()
) works like a charm!
Hi @petreeftime , is there an easy way to call aws_nitro_enclaves_library_seed_entropy
from the command line?
Why doesn't the NSM directly input entropy in the kernel entropy pool?
Why doesn't the NSM directly input entropy in the kernel entropy pool?
This feature was added in https://github.com/aws/aws-nitro-enclaves-sdk-bootstrap/pull/9. The next RPM release should also contain it.
Hi,
I just faced the problem, a brand new enclave has zero entropy:
which causing block when reading from /dev/random early after boot.
What about adding some entropy from NSM RNG at enclave boot stage ?
(in
nitro-cli run-enclave
? ) (or at lower level: I just submitted issue there - https://github.com/aws/aws-nitro-enclaves-sdk-bootstrap/issues/5)Another question: which preferred workaround to use right now?