On 23 July 2018 at 16:16, Theodore Y. Ts'o wrote:
> On Mon, Jul 23, 2018 at 04:43:01AM +0100, Ken Moffat wrote:
>>
>> Did that, no change. Ran strace from the bootscript, confirmed that
>> only /dev/urandom was being used, and that it seemed to be blocking.
>
>
Ted,
last week you proposed an rfc patch to gather entropy from the CPU's
hwrng, and I was pleased - until I discovered one of my stalling
desktop machines does not have a hwrng. At that point I thought that
the problem was only from reading /dev/random, so I went away to look
at persuading the i
On 18 July 2018 at 18:21, Ken Moffat wrote:
> On 18 July 2018 at 02:43, Theodore Ts'o wrote:
>>
>> This will prevent getrandom(2) from blocking, if there is a
>> willingness to trust the CPU manufacturer.
> For me, it seems a price worth paying. I've got bigger
On 18 July 2018 at 02:51, Theodore Y. Ts'o wrote:
> On Tue, Jul 17, 2018 at 09:43:44PM -0400, Theodore Ts'o wrote:
>> This gives the user building their own kernel (or a Linux
>> distribution) the option of deciding whether or not to trust the CPU's
>> hardware random number generator (e.g., RDRAN
