From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
"Theodore Ts'o" <tytso@mit.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
kvm list <kvm@vger.kernel.org>,
Florian Weimer <fweimer@redhat.com>, Kees Cook <kees@outflux.net>
Subject: Re: random: Providing a seed value to VM guests
Date: Thu, 01 May 2014 15:46:20 -0700 [thread overview]
Message-ID: <5362CEBC.9090705@zytor.com> (raw)
In-Reply-To: <CALCETrUe_pFgn27HP4JQ7XpUVJJJoj1PXU5PnznRCEY7mCaaWg@mail.gmail.com>
On 05/01/2014 03:32 PM, Andy Lutomirski wrote:
> On Thu, May 1, 2014 at 3:28 PM, <tytso@mit.edu> wrote:
>> On Thu, May 01, 2014 at 02:06:13PM -0700, Andy Lutomirski wrote:
>>>
>>> I still don't see the point. What does this do better than virtio-rng?
>>
>> I believe you had been complaining about how complicated it was to set
>> up virtio? And this complexity is also an issue if we want to use it
>> to initialize the RNG used for the kernel text ASLR --- which has to
>> be done very early in the boot process, and where making something as
>> simple as possible is a Good Thing.
>
> It's complicated, so it won't be up until much later in the boot
> process. This is completely fine for /dev/random, but it's a problem
> for /dev/urandom, ASLR, and such.
>
>>
>> And since we would want to use RDRAND/RDSEED if it is available
>> *anyway*, perhaps in combination with other things, why not use the
>> RDRAND/RDSEED interface?
>
> Because it's awkward. I don't think it simplifies anything.
>
It greatly simplifies discovery, which is a Big Deal[TM] in early code.
-hpa
next prev parent reply other threads:[~2014-05-01 22:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 19:02 random: Providing a seed value to VM guests Andy Lutomirski
2014-05-01 19:26 ` tytso
2014-05-01 19:40 ` H. Peter Anvin
2014-05-01 20:16 ` Andy Lutomirski
2014-05-01 20:30 ` H. Peter Anvin
2014-05-01 20:32 ` Andy Lutomirski
2014-05-01 20:39 ` tytso
2014-05-01 20:56 ` Andy Lutomirski
2014-05-01 21:01 ` H. Peter Anvin
2014-05-01 21:06 ` Andy Lutomirski
2014-05-01 22:28 ` tytso
2014-05-01 22:32 ` Andy Lutomirski
2014-05-01 22:46 ` H. Peter Anvin [this message]
2014-05-01 22:56 ` Andy Lutomirski
2014-05-01 23:00 ` H. Peter Anvin
2014-05-01 19:41 ` H. Peter Anvin
[not found] <20140428195913.E0A0143994596@oldenburg.str.redhat.com>
[not found] ` <20140428214112.GC7857@thunk.org>
[not found] ` <535FE68C.8060002@redhat.com>
[not found] ` <20140429182610.GA19325@thunk.org>
[not found] ` <53616293.3080308@mit.edu>
[not found] ` <20140501020627.GA25248@thunk.org>
[not found] ` <1be5350d-89f9-44b9-8d1b-e3e591741940@email.android.com>
[not found] ` <20140501150549.GA24388@thunk.org>
[not found] ` <CALCETrUQRqKEbWps5Nxqk57vCYmuvcA6pYAL7OiqJy8sE8yh=g@mail.gmail.com>
2014-05-01 18:53 ` [PATCH] random: Add "initialized" variable to proc Andy Lutomirski
2014-05-01 18:59 ` random: Providing a seed value to VM guests H. Peter Anvin
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=5362CEBC.9090705@zytor.com \
--to=hpa@zytor.com \
--cc=fweimer@redhat.com \
--cc=kees@outflux.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox