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 12:24:50 +0100
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     "Jason A. Donenfeld" <Jason@...c4.com>
Cc:     Theodore Ts'o <tytso@....edu>, 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 Sat, Jan 21, 2017 at 03:08:12PM +0100, Jason A. Donenfeld wrote:
> Hi Ted,
> 
> On Sat, Jan 21, 2017 at 7:24 AM, Theodore Ts'o <tytso@....edu> wrote:
> > Oh, I see.
> >
> > So that's not how I would do things, but it's fine.
> 
> 
> Great, alright. In what tree should I look for these two commits? Or
> should I send it to the drivers/char maintainer (now CCd)?

No objection from me, but as the core stuff is in the networking tree,
maybe it makes more sense for them to flow through there?

Ted, any objection to that?

thanks,

greg k-h