From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Robin Getz <rgetz@blackfin.uclinux.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Chris Peterson <cpeterso@cpeterso.com>,
Matt Mackall <mpm@selenic.com>
Subject: Re: IRQF_SAMPLE_RANDOM question...
Date: Mon, 6 Apr 2009 20:00:25 +0100 [thread overview]
Message-ID: <20090406200025.67cc558a@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <200904061430.26276.rgetz@blackfin.uclinux.org>
On Mon, 6 Apr 2009 14:30:26 -0400
Robin Getz <rgetz@blackfin.uclinux.org> wrote:
> Although there was some discussion
> http://thread.gmane.org/gmane.linux.kernel/680723
>
> about removing IRQF_SAMPLE_RANDOM from the remaining network drivers in May of
> 2008, but they still appears to be there in 2.6.29.
These are mostly unmaintained drivers. Dunno why tg3 isn't fixed - it has
some mitigation logic so maybe its not observable
> I can put a scope/analyser on a device - and look at the touchscreens, serial
> devices, USB, all without cracking the case.
But you can observe a network interface accurately from all over the lan
(and with a ten dollar card), or a good deal further (I believe up to 1Km
in the right conditions was claimed by some
If you need absolute hard entropy then use a real entropy source, if not
then your user space is using the wrong device file - the blocking for
entropy one. At that point it depends how vital your SSL is to you and
what it protects.
Alan
next prev parent reply other threads:[~2009-04-06 19:01 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
2009-04-07 8:27 ` Jeremy Fitzhardinge
2009-04-06 19:22 ` Robin Getz
2009-04-06 19:00 ` Alan Cox [this message]
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=20090406200025.67cc558a@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=cpeterso@cpeterso.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.org \
--cc=rgetz@blackfin.uclinux.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).