From: Ian Campbell <Ian.Campbell@citrix.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Mathew John <mathewj@microsoft.com>,
Theodore Ts'o <tytso@mit.edu>,
David Hepkin <davidhep@microsoft.com>,
kvm list <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Niels Ferguson <niels@microsoft.com>,
Linux Virtualization <virtualization@lists.linux-foundation.org>,
Doug Covelli <dcovelli@vmware.com>,
Jake Oshins <jakeo@microsoft.com>,
David Vrabel <david.vrabel@citrix.com>,
Jim Mattson <jmattson@vmware.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Alok Kataria <akataria@vmware.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
John Starks <John.Starks@microsoft.com>
Subject: Re: [Xen-devel] [RFC] Hypervisor RNG and enumeration
Date: Thu, 30 Oct 2014 15:12:53 +0000 [thread overview]
Message-ID: <1414681973.2064.49.camel@citrix.com> (raw)
In-Reply-To: <CALCETrUp2A27tPb=+9LM4KUmpsRHyKqJM-UB1GApvyQqNu36-Q@mail.gmail.com>
On Thu, 2014-10-30 at 07:45 -0700, Andy Lutomirski wrote:
> > Xen does not have a continual source of entropy and the only feasible
> > way is for the toolstack to provide each guest with a fixed size pool of
> > random data during guest creation.
> >
>
> Xen could seed a very simple per-guest DRBG at guest startup and then
> let the rdmsr call read from it.
I think I'm a bit confused by the intended scope of this facility. The
original spec said:
Note that the CommonHV RNG is not intended to replace stronger, asynchronous
paravirtual random number generator interfaces. It is intended primarily
for seeding guest RNGs early in boot.
Which to me reads that the guest should be using this facility to seed
it's own simple DRBG on boot (with some finite amount of seed data from
the hv) and then using that until it can switch to something better. Is
that not the intention?
I think it's important to nail down the intended scope of this
interface, since it has quite an impact on what would be considered a
reasonable common design.
Post boot I would as you say expect most OSes to switch over to
something more capable, not continue to rely on this facility for the
duration.
Ian.
next prev parent reply other threads:[~2014-10-30 15:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 5:19 [RFC] Hypervisor RNG and enumeration Andy Lutomirski
2014-10-29 10:37 ` [Xen-devel] " Andrew Cooper
2014-10-29 13:45 ` Paolo Bonzini
2014-10-29 13:57 ` David Vrabel
2014-10-29 14:01 ` Paolo Bonzini
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:23 ` Andy Lutomirski
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 16:07 ` H. Peter Anvin
2014-10-29 15:14 ` Ian Jackson
2014-10-29 16:13 ` Andy Lutomirski
2014-10-29 16:29 ` Jake Oshins
2014-10-29 16:50 ` Andy Lutomirski
2014-10-29 18:22 ` Paolo Bonzini
2014-10-30 12:21 ` David Vrabel
2014-10-30 12:25 ` Paolo Bonzini
2014-10-30 14:45 ` Andy Lutomirski
2014-10-30 15:12 ` Ian Campbell [this message]
2014-10-30 14:33 ` Roger Pau Monné
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=1414681973.2064.49.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=John.Starks@microsoft.com \
--cc=akataria@vmware.com \
--cc=david.vrabel@citrix.com \
--cc=davidhep@microsoft.com \
--cc=dcovelli@vmware.com \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=jakeo@microsoft.com \
--cc=jmattson@vmware.com \
--cc=kvm@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mathewj@microsoft.com \
--cc=niels@microsoft.com \
--cc=pbonzini@redhat.com \
--cc=tytso@mit.edu \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).