[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHmME9rObcSGQ9AQOe=4OMK1eszGMgchBznzAZwAO3aaGbo0gQ@mail.gmail.com>
Date: Thu, 22 Jun 2017 02:04:57 +0200
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: "Theodore Ts'o" <tytso@....edu>, Michael Ellerman <mpe@...erman.id.au>,
"Jason A. Donenfeld" <Jason@...c4.com>, Jeffrey Walton <noloader@...il.com>, tglx@...akpoint.cc,
David Miller <davem@...emloft.net>, Linus Torvalds <torvalds@...ux-foundation.org>,
Eric Biggers <ebiggers3@...il.com>, LKML <linux-kernel@...r.kernel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>, kernel-hardening@...ts.openwall.com,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: [PATCH] random: warn when kernel uses unseeded randomness
Hi Ted,
On Wed, Jun 21, 2017 at 10:38 PM, Theodore Ts'o <tytso@....edu> wrote:
> I agree completely with all of this. The following patch replaces the
> current topmost patch on the random.git tree:
> For developers who want to work on improving this situation,
> CONFIG_WARN_UNSEEDED_RANDOM has been renamed to
> CONFIG_WARN_ALL_UNSEEDED_RANDOM. By default the kernel will always
> print the first use of unseeded randomness. This way, hopefully the
> security obsessed will be happy that there is _some_ indication when
> the kernel boots there may be a potential issue with that architecture
> or subarchitecture. To see all uses of unseeded randomness,
> developers can enable CONFIG_WARN_ALL_UNSEEDED_RANDOM.
Seems fine to me.
Acked-by: Jason A. Donenfeld <Jason@...c4.com>
Jason
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
