Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Tue, 31 May 2016 00:39:55 +0200
From: Emese Revfy <>
To: Kees Cook <>
Cc: PaX Team <>, ""
 <>, Brad Spengler
 <>, Michal Marek <>, LKML
 <>, Masahiro Yamada
 <>, linux-kbuild
 <>, "Theodore Ts'o" <>, Andrew
 Morton <>, Linux-MM <>, Jens
 Axboe <>, Al Viro <>, Paul McKenney
 <>, Ingo Molnar <>, Thomas
 Gleixner <>,,
 "David S. Miller" <>
Subject: Re: [PATCH v1 1/3] Add the latent_entropy gcc plugin

On Tue, 24 May 2016 19:55:17 -0700
Kees Cook <> wrote:
> Yeah, answering "how random is this?" is not easy, but that's not what
> I meant. I'm more curious about specific build configs or hardware
> where calling get_random_int() early enough would always produce the
> same value (or the same value across all threads, etc), and in these
> cases, the new entropy should be visible when using the latent entropy
> plugin.

I booted minimal configs (not allnoconfig because it can't boot in qemu)
many times. I couldn't produce same values.


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.