From: "Richard W.M. Jones" <rjones@redhat.com>
To: Cole Robinson <crobinso@redhat.com>, sgrubb@redhat.com
Cc: Peter Krempa <pkrempa@redhat.com>,
mik@miknet.net, libvirt-list@redhat.com,
qemu-devel <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
hkario@redhat.com, hpa@zytor.com,
Amit Shah <amit.shah@redhat.com>,
jjaburek@redhat.com
Subject: Re: [Qemu-devel] [libvirt] RFC: virtio-rng and /dev/urandom
Date: Fri, 15 Apr 2016 12:54:56 +0100 [thread overview]
Message-ID: <20160415115456.GF4810@redhat.com> (raw)
In-Reply-To: <20160415114646.GY11600@redhat.com>
On Fri, Apr 15, 2016 at 12:46:46PM +0100, Richard W.M. Jones wrote:
> On Fri, Apr 15, 2016 at 06:41:34AM -0400, Cole Robinson wrote:
> > Libvirt currently rejects using host /dev/urandom as an input source for a
> > virtio-rng device. The only accepted sources are /dev/random and /dev/hwrng.
> > This is the result of discussions on qemu-devel around when the feature was
> > first added (2013). Examples:
> >
> > http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg02387.html
> > https://lists.gnu.org/archive/html/qemu-devel/2013-03/threads.html#00023
> >
> > libvirt's rejection of /dev/urandom has generated some complaints from users:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1074464
> > * cited: http://www.2uo.de/myths-about-urandom/
> > http://www.redhat.com/archives/libvir-list/2016-March/msg01062.html
> > http://www.redhat.com/archives/libvir-list/2016-April/msg00186.html
> >
> > I think it's worth having another discussion about this, at least with a
> > recent argument in one place so we can put it to bed. I'm CCing a bunch of
> > people. I think the questions are:
> >
> > 1) is the original recommendation to never use virtio-rng+/dev/urandom correct?
> >
> > 2) regardless of #1, should we continue to reject that config in libvirt?
>
> There was a lot of internal-to-Red Hat discussion on this which I
> can't reproduce here unfortunately. However the crux of it was that
> it's quite safe to read enormous amounts from /dev/urandom, even
> without adding any entropy at all, and use those numbers for
> cryptographic purposes.
I should clarify I mean: *after* the pool has been initialized with
sufficient entropy in the first place (which happens very early in
boot), you can then read almost indefinitely.
Rich.
> Steve: can we disclose the research that was done into this? If so
> can you summarise the results for us?
>
> Rich.
>
> --
> Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
> Read my programming and virtualization blog: http://rwmj.wordpress.com
> virt-p2v converts physical machines to virtual machines. Boot with a
> live CD or over the network (PXE) and turn machines into KVM guests.
> http://libguestfs.org/virt-v2v
>
> --
> libvir-list mailing list
> libvir-list@redhat.com
> https://www.redhat.com/mailman/listinfo/libvir-list
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2016-04-15 11:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-15 10:41 [Qemu-devel] RFC: virtio-rng and /dev/urandom Cole Robinson
2016-04-15 11:46 ` Richard W.M. Jones
2016-04-15 11:54 ` Richard W.M. Jones [this message]
2016-04-20 22:48 ` Steve Grubb
2016-04-15 15:47 ` Eric Blake
2016-04-15 16:10 ` Hubert Kario
2016-04-16 0:46 ` H. Peter Anvin
2016-04-16 0:51 ` H. Peter Anvin
2016-04-16 8:31 ` Paolo Bonzini
2016-04-18 0:20 ` H. Peter Anvin
2016-04-18 0:27 ` H. Peter Anvin
2016-04-18 11:21 ` Hubert Kario
2016-04-18 11:00 ` Hubert Kario
2016-04-19 11:30 ` [Qemu-devel] [libvirt] " Yaniv Kaul
2016-04-15 15:56 ` [Qemu-devel] " H. Peter Anvin
2016-04-15 16:06 ` Hubert Kario
2016-04-18 9:28 ` Daniel P. Berrange
2016-04-18 9:46 ` H. Peter Anvin
2016-04-18 11:07 ` Hubert Kario
2016-04-18 11:26 ` Daniel P. Berrange
2016-04-18 21:45 ` H. Peter Anvin
2016-04-20 22:21 ` Cole Robinson
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=20160415115456.GF4810@redhat.com \
--to=rjones@redhat.com \
--cc=amit.shah@redhat.com \
--cc=crobinso@redhat.com \
--cc=hkario@redhat.com \
--cc=hpa@zytor.com \
--cc=jjaburek@redhat.com \
--cc=libvirt-list@redhat.com \
--cc=mik@miknet.net \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=sgrubb@redhat.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.