From: Stephan Mueller Subject: Re: [PATCH v5 0/7] /dev/random - a new approach Date: Tue, 21 Jun 2016 09:32:13 +0200 Message-ID: <24059874.5WizEqNrfz@tauon.atsec.com> References: <2754489.L1QYabbYUc@positron.chronox.de> <1639356.ozYDPrS7jM@tauon.atsec.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: Theodore Ts'o , Pavel Machek , Herbert Xu , Andi Kleen , Sandy Harris , Jason Cooper , John Denker , "H. Peter Anvin" , Joe Perches , George Spelvin , Linux Crypto Mailing List , Linux Kernel Mailing List To: Nikos Mavrogiannopoulos Return-path: Received: from mail.eperm.de ([89.247.134.16]:37582 "EHLO mail.eperm.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932341AbcFUHcU (ORCPT ); Tue, 21 Jun 2016 03:32:20 -0400 In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Am Dienstag, 21. Juni 2016, 09:12:07 schrieb Nikos Mavrogiannopoulos: Hi Nikos, > On Mon, Jun 20, 2016 at 5:43 PM, Stephan Mueller wrote: > >> Personally, I don't really use /dev/random, nor would I recommend it > >> for most application programmers. At this point, getrandom(2) really > >> is the preferred interface unless you have some very specialized > >> needs. > > > > I fully agree. But there are use cases for /dev/random, notably as a seed > > source for other DRNG. > > Is that really the case? I believe all DRNG's use /dev/urandom anyway > for seeding since they cannot afford indeterminate blocking. It would > be a gain for everyone if /dev/random was the same as /dev/urandom in > Linux. For standard approaches, this is true. But there are regulations, notably in the German realm, /dev/random shall be used, at least partially (see AIS 20/31). Ciao Stephan