On 10/6/20 6:29 PM, Samuel Sieb wrote:
On 10/6/20 2:28 PM, Frank McCormick wrote:
My system log is filled with dozens of this line:
localhost.localdomain rngd[638]: Entropy Generation is slow, consider tuning/adding sources
I see that mine is too.
Is this something to be concerned about?
It depends on if you're doing anything that requires entropy. The problem with mine is that it thinks the hwrng is too slow for some reason. I solved this issue by adding a different source. Run "rngd -l" to get a list of available sources: # rngd -l Entropy sources that are available but disabled 1: TPM RNG Device (tpm) 4: NIST Network Entropy Beacon (nist) Available and enabled entropy sources: 0: Hardware RNG Device (hwrng) 5: JITTER Entropy generator (jitter)
I created a file called /etc/systemd/system/rngd.service.d/override.conf and put the following in it: [Service] ExecStart= ExecStart=/sbin/rngd -f -n tpm
Both of those ExecStart lines are necessary. This adds the TPM source. Then run "systemctl daemon-reload" and "systemctl rngd restart". _______________________________________________
Any reason you picked tpm over the others?
I'll give this a shot.
Thanks Samuel
On 10/6/20 4:13 PM, Frank McCormick wrote:
On 10/6/20 6:29 PM, Samuel Sieb wrote:
Entropy sources that are available but disabled 1: TPM RNG Device (tpm) 4: NIST Network Entropy Beacon (nist) Available and enabled entropy sources: 0: Hardware RNG Device (hwrng) 5: JITTER Entropy generator (jitter)
Any reason you picked tpm over the others?
jitter is enabled and not working. hwrng is enabled and not working nist is something over the network All that's left is tpm and if it works, then why not?