linux-kernel - Re: [PATCH -v5] 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: <20140725132225.GQ1865@thunk.org>
Date:	Fri, 25 Jul 2014 09:22:25 -0400
From:	Theodore Ts'o <tytso@....edu>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	Henrique de Moraes Holschuh <hmh@....eng.br>,
	Linux Kernel Developers List <linux-kernel@...r.kernel.org>,
	Linux API <linux-api@...r.kernel.org>,
	linux-crypto@...r.kernel.org
Subject: Re: [PATCH -v5] random: introduce getrandom(2) system call

On Thu, Jul 24, 2014 at 04:27:36PM -0700, Andy Lutomirski wrote:
> 
> I think that people might do:
> 
> try getrandom(GRND_RANDOM)
> fall back to /dev/random
> fall back to something intensely stupid
> 
> We want them to at least attempt the fallback from GRND_RANDOM to !GRND_RANDOM.

We can't legislate against stupidity.  Seriously, the best way to do
this is to write a good userspace library and encourage application
writers to use it.

Regards,

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