From: Stefan Hajnoczi <stefanha@gmail.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: armbru@redhat.com, amit@kernel.org, qemu-devel@nongnu.org,
rjones@redhat.com
Subject: Re: [Qemu-devel] [PATCH] VirtIO-RNG: Update default entropy source to `/dev/urandom`
Date: Thu, 9 May 2019 14:53:20 +0100 [thread overview]
Message-ID: <20190509135320.GE17133@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190503154613.4192-1-kchamart@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1223 bytes --]
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?
>
> Related discussion in these[1][2] past threads.
>
> [1] https://lists.nongnu.org/archive/html/qemu-devel/2018-06/msg08335.html
> -- "RNG: Any reason QEMU doesn't default to `/dev/urandom`?"
> [2] https://lists.nongnu.org/archive/html/qemu-devel/2018-09/msg02724.html
> -- "[RFC] Virtio RNG: Consider changing the default entropy source to
> /dev/urandom"
Please include actual justification in the commit description instead of
linking to email threads that need to be read and interpreted.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-09 13:54 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 [this message]
2019-05-09 14:54 ` Daniel P. Berrangé
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=20190509135320.GE17133@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=amit@kernel.org \
--cc=armbru@redhat.com \
--cc=kchamart@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@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 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).