Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
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
Thread-Topic: Stop breaking the CSRNG
Thread-Index: AQHVeUNxp+fni2lQz0uk1fV0/DAY1qdIrV6A
Date:   Thu, 3 Oct 2019 10:13:39 +0000
Message-ID: <b193685d90c0474aa0727555f936528b@AcuMS.aculab.com>
References: <20191002165533.GA18282@roeckx.be>
In-Reply-To: <20191002165533.GA18282@roeckx.be>
Accept-Language: en-GB, en-US
Content-Language: en-US
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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)