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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 22 Jan 2017 13:21:39 +0100
From:   "Jason A. Donenfeld" <Jason@...c4.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
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

Hey Greg,

On Sun, Jan 22, 2017 at 12:24 PM, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> 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?

The core stuff is not in the networking tree. This is nothing to do
with the networking tree in any way at all. There might be some
confusion because the initial discussions came from the siphash stuff,
which is in the networking tree, but Ted and I choose a different
route, going with chacha instead of siphash. So this is 0%
network-related.

> Ted, any objection to that?

Seems like either you pull or Ted pulls it.

Jason