From: David Laight <David.Laight@ACULAB.COM>
To: 'Kurt Roeckx' <kurt@roeckx.be>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: RE: Stop breaking the CSRNG
Date: Thu, 3 Oct 2019 10:13:39 +0000 [thread overview]
Message-ID: <b193685d90c0474aa0727555f936528b@AcuMS.aculab.com> (raw)
In-Reply-To: <20191002165533.GA18282@roeckx.be>
From: Kurt Roeckx
> Sent: 02 October 2019 17:56
> As OpenSSL, we want cryptograhic secure random numbers. Before
> getrandom(), Linux never provided a good API for that, both
> /dev/random and /dev/urandom have problems. getrandom() fixed
> that, so we switched to it were available.
The fundamental problem is that you can't always get ' cryptograhic secure
random numbers'. No API changes are ever going to change that.
The system can either return an error or sleep (possibly indefinitely)
until some 'reasonably random' numbers are available.
A RISC-V system running on an FGPA (I've only used Altera NIOS cpu)
may have absolutely no sources of randomness at boot time.
Saying the architecture must include a random number instruction
doesn't help!
Generating random bits inside the FPGA is somewhere between 'difficult'
and impossible (forcing metastability between clock domains might work).
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2019-10-03 10:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 16:55 Kurt Roeckx
2019-10-03 3:36 ` Theodore Y. Ts'o
2019-10-03 21:14 ` Kurt Roeckx
2019-10-06 12:15 ` Pavel Machek
2019-10-03 10:13 ` David Laight [this message]
2019-10-03 11:51 ` Adam Borowski
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=b193685d90c0474aa0727555f936528b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=kurt@roeckx.be \
--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
all inboxes | Powered by JetHome®