mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, Jason@zx2c4.com
Subject: Re: [PULL] random changes for 3.11
Date: Fri, 10 Mar 2017 12:40:19 -0500	[thread overview]
Message-ID: <20170310174018.a3cbbucmubswsxw6@thunk.org> (raw)
In-Reply-To: <20170310151649.jek5t3xy5oy7m5uo@thunk.org>

Oops, sorry, I forgot to CC the linux-kernel mailing list.

      	       	      	     - Ted

On Fri, Mar 10, 2017 at 10:16:49AM -0500, Theodore Ts'o wrote:
> Hi Linus,
> 
> Apologies this pull request is late.  Between travel for the FAST
> conference, performance review, and paper review deadlines for Usenix
> ATC, this just fell between the cracks.
> 
> There's nothing particularly risky or controversial here; the biggest
> change was getting rid of the MD5 rng and replacing it with the
> ChaCha20 based CRNG that we use for /dev/random and getrandom(2).
> It's faster, more secure, and deletes code.
> 
> Thanks,
> 
>      	     	  	      	      - Ted
> 
> The following changes since commit a121103c922847ba5010819a3f250f1f7fc84ab8:
> 
>   Linux 4.10-rc3 (2017-01-08 14:18:17 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus
> 
> for you to fetch changes up to db61ffe3a71c697aaa91c42c862a5f7557a0e562:
> 
>   random: move random_min_urandom_seed into CONFIG_SYSCTL ifdef block (2017-02-06 20:46:49 -0500)
> 
> ----------------------------------------------------------------
> Change get_random_{int,log} to use the CRNG used by /dev/urandom and
> getrandom(2).  It's faster and arguably more secure than cut-down MD5
> that we had been using.
> 
> Also do some code cleanup.
> 
> ----------------------------------------------------------------
> Fabio Estevam (1):
>       random: move random_min_urandom_seed into CONFIG_SYSCTL ifdef block
> 
> Jason A. Donenfeld (2):
>       random: use chacha20 for get_random_int/long
>       random: convert get_random_int/long into get_random_u32/u64
> 
> Stephan Mueller (1):
>       random: remove stale maybe_reseed_primary_crng
> 
> Stephan Müller (3):
>       random: remove stale urandom_init_wait
>       random: remove variable limit
>       random: fix comment for unused random_min_urandom_seed
> 
>  drivers/char/random.c  | 129 +++++++++++++++++++++++++++++++++++-------------------------------------------------------
>  include/linux/random.h |  18 ++++++++++---
>  init/main.c            |   1 -
>  3 files changed, 65 insertions(+), 83 deletions(-)

           reply	other threads:[~2017-03-10 18:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20170310151649.jek5t3xy5oy7m5uo@thunk.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170310174018.a3cbbucmubswsxw6@thunk.org \
    --to=tytso@mit.edu \
    --cc=Jason@zx2c4.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®