linux-kernel - Re: [PATCH] random: add a config option to trust the CPU's hwrng

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANVEwpbcaTq=gFHVi0FUjq=7vLbQNYRX7aBRxWvH68oY_LFm-A@mail.gmail.com>
Date:   Thu, 19 Jul 2018 01:19:27 +0100
From:   Ken Moffat <zarniwhoop73@...glemail.com>
To:     "Theodore Y. Ts'o" <tytso@....edu>, linux-crypto@...r.kernel.org,
        Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
        labbott@...hat.com
Subject: Re: [PATCH] random: add a config option to trust the CPU's hwrng

On 18 July 2018 at 18:21, Ken Moffat <zarniwhoop73@...glemail.com> wrote:
> On 18 July 2018 at 02:43, Theodore Ts'o <tytso@....edu> 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 problems than
> _worriying_ about my government, or yours, spying on me, so I'd like to take
> the risk.
>
Sadly, my enthusiasm was premature: the Kaveri doesn't have a hwrng. So
although I've enabled the device under the HW_RANDOM options, nothing
comes out and this "fix" will only work for some machines.

For me, I'll have to go to plan B (revise the bootscript and/or patch unbound).
I see that Nixos seems to bind /dev/urandom to /var/lib/unbound/dev/random
so I guess that ought to work. Sorry for the noise.

ĸen