Re: [PATCH 3/8] random: trigger random_ready callback upon crng_init == 1

From	Theodore Ts'o <tytso@mit.edu>
Newsgroups	linux.kernel
Subject	Re: [PATCH 3/8] random: trigger random_ready callback upon crng_init == 1
Date	2017-01-18 06:00 +0100
Message-ID	<t0QvM-7Ve-11@gated-at.bofh.it> (permalink)
References	<sT8Jb-86X-3@gated-at.bofh.it> <sT8Jb-86X-7@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Tue, Dec 27, 2016 at 11:39:57PM +0100, Stephan Müller wrote:
> The random_ready callback mechanism is intended to replicate the
> getrandom system call behavior to in-kernel users. As the getrandom
> system call unblocks with crng_init == 1, trigger the random_ready
> wakeup call at the same time.

It was deliberate that random_ready would only get triggered with
crng_init==2.

In general I'm assuming kernel callers really want real randomness (as
opposed to using prandom), where as there's a lot of b.s. userspace
users of kernel randomness (for things that really don't require
cryptographic randomness, e.g., for salting Python dictionaries,
systemd/udev using /dev/urandom for non-cryptographic, non-security
applications etc.)

						- Ted

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: [PATCH 3/8] random: trigger random_ready callback upon crng_init  == 1 Theodore Ts'o <tytso@mit.edu> - 2017-01-18 06:00 +0100
  Re: [PATCH 3/8] random: trigger random_ready callback upon crng_init == 1 Stephan Müller <smueller@chronox.de> - 2017-01-18 18:20 +0100

csiph-web