[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALCETrWeWQeotMXbY2yKOmWbhW7HZLYdFBUVcFy3vCmSnm+9Sw@mail.gmail.com>
Date: Fri, 20 Sep 2019 07:46:19 -0700
From: Andy Lutomirski <luto@...nel.org>
To: Andy Lutomirski <luto@...nel.org>
Cc: Theodore Tso <tytso@...gle.com>,
LKML <linux-kernel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Kees Cook <keescook@...omium.org>,
"Jason A. Donenfeld" <Jason@...c4.com>,
"Ahmed S. Darwish" <darwish.07@...il.com>,
Lennart Poettering <mzxreary@...inter.de>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Alexander E. Patrakov" <patrakov@...il.com>,
Michael Kerrisk <mtk.manpages@...il.com>,
Willy Tarreau <w@....eu>,
Matthew Garrett <mjg59@...f.ucam.org>,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
linux-man <linux-man@...r.kernel.org>
Subject: Re: [PATCH v2 0/7] Rework random blocking
On Fri, Sep 20, 2019 at 7:36 AM Andy Lutomirski <luto@...nel.org> wrote:
>
> This makes two major semantic changes to Linux's random APIs:
Hmm. I have at least two issues in here that need fixing:
- getrandom() can warn. Whoops.
- Repeatedly calling getentropy in GRND_INSECURE mode will interfere
will CRNG init.
v3 will fix these issues.
Powered by blists - more mailing lists