linux-kernel - Re: [PATCH -v4] 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]

Date:	Mon, 21 Jul 2014 18:23:22 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	linux-kernel@...r.kernel.org, linux-api@...r.kernel.org,
	linux-crypto@...r.kernel.org, beck@...nbsd.org,
	deraadt@....openbsd.org
Subject: Re: [PATCH -v4] random: introduce getrandom(2) system call

On Mon, Jul 21, 2014 at 10:21:26PM +0200, Till Smejkal wrote:
> Hi,
> 
> On Fri, 18 Jul 2014, Theodore Ts'o wrote:
> [...]
> > 	If the GRND_RANDOM bit is not set, then the /dev/urandom pool
> > 	will be used.  Unlike using read(2) to fetch data from
> > 	/dev/urandom, if the urandom pool has not been sufficiently
> > 	initialized, getrandom(2) will block or return -1 with the
> > 	errno set to EGAIN if the GRND_NONBLOCK bit is set in flags.
>                  ^^^^^
> Small typo: this should be EAGAIN.

Thanks for pointing this out!  Will fix.

					- Ted
--
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/