From: Florian Weimer Subject: Re: [PATCH v24 00/12] /dev/random - a new approach with full SP800-90B compliance Date: Tue, 12 Nov 2019 14:23:10 +0100 Message-ID: <875zjpfcu9.fsf@mid.deneb.enyo.de> References: <6157374.ptSnyUpaCn@positron.chronox.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Return-path: In-Reply-To: <6157374.ptSnyUpaCn@positron.chronox.de> ("Stephan \=\?iso-8859-1\?Q\?M\=FCller\=22's\?\= message of "Mon, 11 Nov 2019 19:17:30 +0100") Sender: linux-kernel-owner@vger.kernel.org To: Stephan =?iso-8859-1?Q?M=FCller?= Cc: Arnd Bergmann , Greg Kroah-Hartman , linux-crypto@vger.kernel.org, LKML , linux-api@vger.kernel.org, "Eric W. Biederman" , "Alexander E. Patrakov" , "Ahmed S. Darwish" , "Theodore Y. Ts'o" , Willy Tarreau , Matthew Garrett , Vito Caputo , Andreas Dilger , Jan Kara , Ray Strode , William Jon McCann , zhangjs , Andy Lutomirski , Florian Weimer , Lennart Poettering , Nicolai Stange List-Id: linux-api@vger.kernel.org * Stephan Müller: > * support deactivation of TRNG (i.e. blocking behavior of /dev/random) > at compile time. If deactivated, /dev/random behaves like > getrandom(2). I don't quite understand this comment. Doesn't getrandom with the GRND_RANDOM always behave like /dev/random? Presumably, without the TRNG tap, the GRND_RANDOM flag for getrandom is ignored, and reading from /dev/random behaves like reading from /dev/urandom. Anyway, reading the accompanying PDF, this looks rather impressive: the userspace bootstrapping problem is gone (the issue where waiting for more entropy prevents the collection of more entropy), *and* we can still make the standards people happy. (Replying from my other account due to mail issues, sorry.)