linux-kernel - Re: [PATCH, RFC -v2] random: introduce getrandom(2) system call

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <53C8EB45.20304@redhat.com>
Date:	Fri, 18 Jul 2014 11:39:17 +0200
From:	Florian Weimer <fweimer@...hat.com>
To:	"Theodore Ts'o" <tytso@....edu>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>
CC:	linux-crypto@...r.kernel.org, linux-api@...r.kernel.org,
	beck@...nbsd.org
Subject: Re: [PATCH, RFC -v2] random: introduce getrandom(2) system call

On 07/17/2014 11:38 PM, Theodore Ts'o wrote:
> 	If the GRND_RANDOM flags bit is set, then draw from the
> 	/dev/random pool instead of the /dev/urandom pool.  The
> 	/dev/random pool is limited based on the entropy that can be
> 	obtained from environmental noise, so if there is insufficient
> 	entropy, the requested number of bytes may not be returned.
> 	If there is no entropy available at all, getrandom(2) will
> 	either block, or return an error with errno set to EAGAIN if
> 	the GRND_NONBLOCK bit is set in flags.

Can we get a GRND_INIT flag or something like that which means 
"block/return EAGAIN until the kernel pool is initialized"?  Thanks.

(See the previous discussion about pool initialization.)

-- 
Florian Weimer / Red Hat Product Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/