From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: PaX Team <pageexec@freemail.hu>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Brad Spengler <spender@grsecurity.net>,
Michal Marek <mmarek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>, Jens Axboe <axboe@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
bart.vanassche@sandisk.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v1 1/3] Add the latent_entropy gcc plugin
Date: Tue, 31 May 2016 00:39:55 +0200 [thread overview]
Message-ID: <20160531003955.032d11cad95c4439328b0128@gmail.com> (raw)
In-Reply-To: <CAGXu5jJ4iOHw+9khys3HVKAJH6q4Vu+8aSabycYWUCdK9GonKw@mail.gmail.com>
On Tue, 24 May 2016 19:55:17 -0700
Kees Cook <keescook@chromium.org> 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.
--
Emese
WARNING: multiple messages have this Message-ID (diff)
From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: PaX Team <pageexec@freemail.hu>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Brad Spengler <spender@grsecurity.net>,
Michal Marek <mmarek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>, Jens Axboe <axboe@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
bart.vanassche@sandisk.com,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v1 1/3] Add the latent_entropy gcc plugin
Date: Tue, 31 May 2016 00:39:55 +0200 [thread overview]
Message-ID: <20160531003955.032d11cad95c4439328b0128@gmail.com> (raw)
In-Reply-To: <CAGXu5jJ4iOHw+9khys3HVKAJH6q4Vu+8aSabycYWUCdK9GonKw@mail.gmail.com>
On Tue, 24 May 2016 19:55:17 -0700
Kees Cook <keescook@chromium.org> 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.
--
Emese
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Emese Revfy <re.emese@gmail.com>
To: Kees Cook <keescook@chromium.org>
Cc: PaX Team <pageexec@freemail.hu>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Brad Spengler <spender@grsecurity.net>,
Michal Marek <mmarek@suse.com>,
LKML <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Andrew Morton <akpm@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>, Jens Axboe <axboe@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
bart.vanassche@sandisk.com,
"David S. Miller" <davem@davemloft.net>
Subject: [kernel-hardening] Re: [PATCH v1 1/3] Add the latent_entropy gcc plugin
Date: Tue, 31 May 2016 00:39:55 +0200 [thread overview]
Message-ID: <20160531003955.032d11cad95c4439328b0128@gmail.com> (raw)
In-Reply-To: <CAGXu5jJ4iOHw+9khys3HVKAJH6q4Vu+8aSabycYWUCdK9GonKw@mail.gmail.com>
On Tue, 24 May 2016 19:55:17 -0700
Kees Cook <keescook@chromium.org> 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.
--
Emese
next prev parent reply other threads:[~2016-05-30 22:33 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 22:14 [PATCH v1 0/3] Introduce the latent_entropy gcc plugin Emese Revfy
2016-05-23 22:14 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:14 ` Emese Revfy
2016-05-23 22:15 ` [PATCH v1 1/3] Add " Emese Revfy
2016-05-23 22:15 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:15 ` Emese Revfy
2016-05-24 17:32 ` Kees Cook
2016-05-24 17:32 ` [kernel-hardening] " Kees Cook
2016-05-24 17:32 ` Kees Cook
2016-05-24 17:32 ` Kees Cook
2016-05-24 21:23 ` Emese Revfy
2016-05-24 21:23 ` [kernel-hardening] " Emese Revfy
2016-05-24 21:23 ` Emese Revfy
2016-05-24 21:23 ` Emese Revfy
2016-05-24 23:40 ` PaX Team
2016-05-24 23:40 ` [kernel-hardening] " PaX Team
2016-05-24 23:40 ` PaX Team
2016-05-24 23:40 ` PaX Team
2016-05-25 2:55 ` Kees Cook
2016-05-25 2:55 ` [kernel-hardening] " Kees Cook
2016-05-25 2:55 ` Kees Cook
2016-05-25 2:55 ` Kees Cook
2016-05-30 22:39 ` Emese Revfy [this message]
2016-05-30 22:39 ` [kernel-hardening] " Emese Revfy
2016-05-30 22:39 ` Emese Revfy
2016-05-30 22:39 ` Emese Revfy
2016-05-23 22:16 ` [PATCH v1 2/3] Mark functions with the latent_entropy attribute Emese Revfy
2016-05-23 22:16 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:16 ` Emese Revfy
2016-05-24 17:16 ` Kees Cook
2016-05-24 17:16 ` [kernel-hardening] " Kees Cook
2016-05-24 17:16 ` Kees Cook
2016-05-24 17:16 ` Kees Cook
2016-05-24 20:45 ` Emese Revfy
2016-05-24 20:45 ` [kernel-hardening] " Emese Revfy
2016-05-24 20:45 ` Emese Revfy
2016-05-24 20:45 ` Emese Revfy
2016-05-24 20:55 ` Kees Cook
2016-05-24 20:55 ` [kernel-hardening] " Kees Cook
2016-05-24 20:55 ` Kees Cook
2016-05-24 20:55 ` Kees Cook
2016-05-23 22:17 ` [PATCH v1 3/3] Add the extra_latent_entropy kernel parameter Emese Revfy
2016-05-23 22:17 ` [kernel-hardening] " Emese Revfy
2016-05-23 22:17 ` Emese Revfy
2016-05-24 17:09 ` Kees Cook
2016-05-24 17:09 ` [kernel-hardening] " Kees Cook
2016-05-24 17:09 ` Kees Cook
2016-05-24 17:09 ` Kees Cook
2016-05-24 20:29 ` Emese Revfy
2016-05-24 20:29 ` [kernel-hardening] " Emese Revfy
2016-05-24 20:29 ` Emese Revfy
2016-05-24 20:29 ` Emese Revfy
2016-05-29 17:59 [PATCH v1 1/3] Add the latent_entropy gcc plugin Hector Martin
2016-05-30 2:16 ` Kees Cook
2016-05-30 3:46 ` Hector Martin "marcan"
2016-05-30 15:40 ` Kees Cook
2016-05-30 20:24 ` Hector Martin "marcan"
2016-05-31 17:25 ` Kees Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160531003955.032d11cad95c4439328b0128@gmail.com \
--to=re.emese@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=bart.vanassche@sandisk.com \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.com \
--cc=pageexec@freemail.hu \
--cc=paulmck@linux.vnet.ibm.com \
--cc=spender@grsecurity.net \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.