From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>,
"Theodore Ts'o" <tytso@mit.edu>,
Florian Weimer <fweimer@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Kees Cook <kees@outflux.net>, kvm list <kvm@vger.kernel.org>
Subject: random: Providing a seed value to VM guests
Date: Thu, 01 May 2014 11:59:25 -0700 [thread overview]
Message-ID: <5362998D.3030102@zytor.com> (raw)
In-Reply-To: <CALCETrWwcuq_-Q+i1g9hspsddGUmx8_yf3EaOLjgPcF5+yBnYA@mail.gmail.com>
On 05/01/2014 11:53 AM, Andy Lutomirski wrote:
>
> A CPUID leaf or an MSR advertised by a CPUID leaf has another
> advantage: it's easy to use in the ASLR code -- I don't think there's
> a real IDT, so there's nothing like rdmsr_safe available. It also
> avoids doing anything complicated with the boot process to allow the
> same seed to be used for ASLR and random.c; it can just be invoked
> twice on boot.
>
At that point we are talking an x86-specific interface, and so we might
as well simply emulate RDRAND (urandom) and RDSEED (random) if the CPU
doesn't support them. I believe KVM already has a way to report CPUID
features that are "emulated but supported anyway", i.e. they work but
are slow.
> What's the right forum for this? This thread is probably not it.
Change the subject line?
-hpa
next prev parent reply other threads:[~2014-05-01 18:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 19:52 [PATCH] random: Add "initialized" variable to proc Florian Weimer
2014-04-28 21:41 ` Theodore Ts'o
2014-04-29 17:51 ` Florian Weimer
2014-04-29 18:26 ` Theodore Ts'o
2014-04-30 20:52 ` Andy Lutomirski
2014-05-01 2:06 ` Theodore Ts'o
2014-05-01 4:05 ` H. Peter Anvin
2014-05-01 15:05 ` tytso
2014-05-01 15:35 ` Andy Lutomirski
2014-05-01 18:53 ` Andy Lutomirski
2014-05-01 18:59 ` H. Peter Anvin [this message]
2014-05-01 5:37 ` H. Peter Anvin
2014-05-01 14:33 ` Jason Cooper
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
2014-05-01 22:56 ` Andy Lutomirski
2014-05-01 23:00 ` H. Peter Anvin
2014-05-01 19:41 ` 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=5362998D.3030102@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
Powered by JetHome