From: Ken Moffat <zarniwhoop73@googlemail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
linux-crypto@vger.kernel.org,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
labbott@redhat.com
Subject: Re: [PATCH] random: add a config option to trust the CPU's hwrng
Date: Thu, 19 Jul 2018 01:19:27 +0100 [thread overview]
Message-ID: <CANVEwpbcaTq=gFHVi0FUjq=7vLbQNYRX7aBRxWvH68oY_LFm-A@mail.gmail.com> (raw)
In-Reply-To: <CANVEwpY2H+OBnYNAf15bRRbmepFCerWrisLiLQ=h3+_692MY7A@mail.gmail.com>
On 18 July 2018 at 18:21, Ken Moffat <zarniwhoop73@googlemail.com> wrote:
> On 18 July 2018 at 02:43, Theodore Ts'o <tytso@mit.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
next prev parent reply other threads:[~2018-07-19 0:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-18 1:43 [PATCH] random: add a config option to trust the CPU's hwrng Theodore Ts'o
2018-07-18 1:51 ` Theodore Y. Ts'o
2018-07-18 15:14 ` Sandy Harris
2018-07-18 17:36 ` [PATCH] random: addu " Theodore Y. Ts'o
2018-07-18 20:22 ` Sandy Harris
2018-07-19 14:21 ` Theodore Y. Ts'o
2018-07-19 20:17 ` Yann Droneaud
2018-07-18 17:36 ` [PATCH] random: add " Ken Moffat
2018-07-19 0:19 ` Ken Moffat [this message]
2018-07-18 5:09 ` Randy Dunlap
2018-07-18 6:46 ` Jeffrey Walton
2018-07-18 7:22 ` Yann Droneaud
2018-07-18 14:26 ` Theodore Y. Ts'o
2018-07-18 15:29 ` Yann Droneaud
2018-07-18 19:17 ` Theodore Y. Ts'o
2018-08-04 21:52 ` Pavel Machek
2018-08-05 0:25 ` Theodore Y. Ts'o
2018-08-05 0:28 ` Theodore Y. Ts'o
2018-08-05 9:44 ` Pavel Machek
2018-07-20 19:09 ` Laura Abbott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANVEwpbcaTq=gFHVi0FUjq=7vLbQNYRX7aBRxWvH68oY_LFm-A@mail.gmail.com' \
--to=zarniwhoop73@googlemail.com \
--cc=labbott@redhat.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).