From: Jeff Garzik <jeff@garzik.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Robin Getz <rgetz@blackfin.uclinux.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Peterson <cpeterso@cpeterso.com>,
Matt Mackall <mpm@selenic.com>,
David Miller <davem@davemloft.net>
Subject: Re: IRQF_SAMPLE_RANDOM question...
Date: Mon, 06 Apr 2009 14:49:48 -0400 [thread overview]
Message-ID: <49DA4ECC.9050204@garzik.org> (raw)
In-Reply-To: <20090406114432.3a554eba@nehalam>
Stephen Hemminger wrote:
> The real problem one is xen-netfront. Because 1) it is least random,
> the attacker might be another VM 2) the VM is most in need of random
> samples because it doesn't have real hardware.
Agreed.
I'm surprised Xen doesn't use virtio-rng. I guess it needs a special
Xen paravirt driver for randomness.
Jeff
next prev parent reply other threads:[~2009-04-06 18:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 18:30 IRQF_SAMPLE_RANDOM question Robin Getz
2009-04-06 18:40 ` Jeff Garzik
2009-04-06 18:44 ` Stephen Hemminger
2009-04-06 18:49 ` Jeff Garzik [this message]
2009-04-07 8:27 ` Jeremy Fitzhardinge
2009-04-06 19:22 ` Robin Getz
2009-04-06 19:00 ` Alan Cox
2009-04-06 19:01 ` Matt Mackall
2009-04-06 22:09 ` Sven-Haegar Koch
2009-04-06 23:35 ` Jeff Garzik
2009-04-07 21:58 ` Robin Getz
2009-04-07 22:25 ` Jeff Garzik
2009-04-07 0:16 ` Matt Mackall
2009-04-07 0:30 ` Jeff Garzik
2009-04-07 11:16 ` Robin Getz
2009-04-07 14:57 ` Matt Mackall
2009-04-07 21:39 ` Chris Peterson
2009-04-07 22:30 ` Robin Getz
2009-04-08 21:53 ` Gilles Espinasse
2009-04-08 23:16 ` Chris Friesen
2009-04-09 4:24 ` Robin Getz
2009-04-07 21:44 ` Robin Getz
2009-04-08 19:51 ` Matt Mackall
2009-04-09 13:54 ` Robin Getz
2009-04-09 17:00 ` Matt Mackall
2009-04-10 0:41 ` Robin Getz
2009-04-10 1:29 ` Chris Peterson
2009-04-10 2:27 ` Matt Mackall
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=49DA4ECC.9050204@garzik.org \
--to=jeff@garzik.org \
--cc=cpeterso@cpeterso.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.org \
--cc=shemminger@vyatta.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.