From: Anthony Liguori <anthony@codemonkey.ws>
To: Amit Shah <amit.shah@redhat.com>
Cc: qemu list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] virtio-rng: device to send host entropy to guest
Date: Wed, 16 May 2012 13:23:11 -0500 [thread overview]
Message-ID: <4FB3F08F.2070303@codemonkey.ws> (raw)
In-Reply-To: <20120516172143.GA16342@amit.redhat.com>
On 05/16/2012 12:21 PM, Amit Shah wrote:
> On (Wed) 16 May 2012 [08:24:22], Anthony Liguori wrote:
>> On 05/16/2012 06:30 AM, Amit Shah wrote:
>>> The Linux kernel already has a virtio-rng driver, this is the device
>>> implementation.
>>>
>>> When Linux needs more entropy, it puts a buffer in the vq. We then put
>>> entropy into that buffer, and push it back to the guest.
>>>
>>> Feeding randomness from host's /dev/urandom into the guest is
>>> sufficient, so this is a simple implementation that opens /dev/urandom
>>> and reads from it whenever required.
>>>
>>> Invocation is simple:
>>>
>>> qemu ... -device virtio-rng-pci
>>>
>>> In the guest, we see
>>>
>>> $ cat /sys/devices/virtual/misc/hw_random/rng_available
>>> virtio
>>>
>>> $ cat /sys/devices/virtual/misc/hw_random/rng_current
>>> virtio
>>>
>>> There are ways to extend the device to be more generic and collect
>>> entropy from other sources, but this is simple enough and works for now.
>>>
>>> Signed-off-by: Amit Shah<amit.shah@redhat.com>
>>
>> It's not this simple unfortunately.
>>
>> If you did this with libvirt, one guest could exhaust the available
>> entropy for the remaining guests. This could be used as a mechanism
>> for one guest to attack another (reducing the available entropy for
>> key generation).
>>
>> You need to rate limit the amount of entropy that a guest can obtain
>> to allow management tools to mitigate this attack.
>
> Hm, rate-limiting is a good point. However, we're using /dev/urandom
> here, which is nonblocking, and will keep on providing data as long as
> we keep reading.
But you're still exhausting the entropy pool (which is a global resource).
That's the problem.
Regards,
Anthony Liguori
>
> Amit
next prev parent reply other threads:[~2012-05-16 18:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 11:30 [Qemu-devel] [PATCH 1/1] virtio-rng: device to send host entropy to guest Amit Shah
2012-05-16 11:38 ` Paolo Bonzini
2012-05-16 11:54 ` Amit Shah
2012-05-16 13:24 ` Anthony Liguori
2012-05-16 13:45 ` Daniel P. Berrange
2012-05-16 13:48 ` Anthony Liguori
2012-05-16 13:53 ` Daniel P. Berrange
2012-05-16 14:02 ` Anthony Liguori
2012-05-16 17:28 ` Amit Shah
2012-05-21 19:32 ` Amit Shah
2012-05-16 17:26 ` Amit Shah
2012-05-16 18:24 ` Anthony Liguori
2012-05-21 19:37 ` Amit Shah
2012-05-16 17:21 ` Amit Shah
2012-05-16 18:23 ` Anthony Liguori [this message]
2012-05-21 19:39 ` Amit Shah
2012-05-21 20:34 ` Anthony Liguori
2012-05-22 12:57 ` Amit Shah
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=4FB3F08F.2070303@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.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).