linux-kernel - Re: [PATCH 1/2] random: use chacha20 for get_random

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:   Sun, 22 Jan 2017 19:33:17 -0500
From:   Theodore Ts'o <tytso@....edu>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        LKML <linux-kernel@...r.kernel.org>,
        Hannes Frederic Sowa <hannes@...essinduktion.org>,
        Andy Lutomirski <luto@...capital.net>
Subject: Re: [PATCH 1/2] random: use chacha20 for get_random_int/long

On Sun, Jan 22, 2017 at 11:49:00PM +0100, Jason A. Donenfeld wrote:
> On Sun, Jan 22, 2017 at 11:28 PM, Theodore Ts'o <tytso@....edu> wrote:
> > If there are other changes to the relevant lines from the networking
> > tree, sure.
> 
> This patch set has *nothing* to do with the networking tree. That just
> a topic confusion. There shouldn't be more discussion about
> networking, because it doesn't make sense in any way at all.

Well, the reason people do is for hysterical... er, historical
reasons.  *Originaly* get_random_int() was introduced for use by the
networking folks, and some people think that get_random_int()
therefore "belongs" to the networking tree, even though there are
other users of get_random_int() and get_random_long() besides the
networking code.

I'd much rather break this obviously historical connection, but
patching people's wetware is a lot harder than getting a patch into
the kernel tree....

						- Ted