From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel@nongnu.org, rjones@redhat.com, amit@kernel.org,
armbru@redhat.com, Kashyap Chamarthy <kchamart@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] VirtIO-RNG: Update default entropy source to `/dev/urandom`
Date: Thu, 9 May 2019 15:54:47 +0100 [thread overview]
Message-ID: <20190509145447.GG31299@redhat.com> (raw)
In-Reply-To: <20190509135320.GE17133@stefanha-x1.localdomain>
On Thu, May 09, 2019 at 02:53:20PM +0100, Stefan Hajnoczi wrote:
> On Fri, May 03, 2019 at 05:46:12PM +0200, Kashyap Chamarthy wrote:
> > When QEMU exposes a VirtIO-RNG device to the guest, that device needs a
> > source of entropy, and that source needs to be "non-blocking", like
> > `/dev/urandom`. However, currently QEMU defaults to the problematic
> > `/dev/random`, which is "blocking" (as in, it waits until sufficient
> > entropy is available).
> >
> > So change the entropy source to the recommended `/dev/urandom`.
>
> Why is /dev/urandom "recommended"?
>
> I understand the requirement for instant random numbers, but what about
> the concerns about quality? Have you decided that the consumers of
> these random numbers are safe with /dev/urandom?
The current random(4) man page says:
The /dev/random interface is considered a legacy inter‐
face, and /dev/urandom is preferred and sufficient in
all use cases, with the exception of applications which
require randomness during early boot time; for these
applications, getrandom(2) must be used instead,
because it will block until the entropy pool is ini‐
tialized.
"early boot" is a bit of an ill-defined term here, but I think in
general QEMU can reasonably be said to not be running in early boot.
In any case the newly proposed RNG backend should ultimately become
the preferred choice for mgmt apps:
https://lists.gnu.org/archive/html/qemu-devel/2019-05/msg02062.html
This new rng-builtin delegates to our crypto random APIs, which are
backed by GNUTLS, libgcrypt, getrandom (or Windows equiv), and
finally /dev/urandom as last ditch effort.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-05-09 14:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 15:46 [Qemu-devel] [PATCH] VirtIO-RNG: Update default entropy source to `/dev/urandom` Kashyap Chamarthy
2019-05-03 15:46 ` Kashyap Chamarthy
2019-05-03 15:46 ` Kashyap Chamarthy
2019-05-03 15:46 ` Kashyap Chamarthy
2019-05-03 15:49 ` Daniel P. Berrangé
2019-05-03 15:49 ` Daniel P. Berrangé
2019-05-03 20:47 ` Kashyap Chamarthy
2019-05-03 20:47 ` Kashyap Chamarthy
2019-05-07 9:43 ` Daniel P. Berrangé
2019-05-03 16:11 ` Richard W.M. Jones
2019-05-03 16:11 ` Richard W.M. Jones
2019-05-07 15:20 ` Richard Henderson
2019-05-09 13:53 ` Stefan Hajnoczi
2019-05-09 14:54 ` Daniel P. Berrangé [this message]
2019-05-09 15:59 ` Kashyap Chamarthy
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=20190509145447.GG31299@redhat.com \
--to=berrange@redhat.com \
--cc=amit@kernel.org \
--cc=armbru@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--cc=stefanha@gmail.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 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).