From: Robin Getz <rgetz@blackfin.uclinux.org>
To: "Chris Peterson" <cpeterso@cpeterso.com>
Cc: "Matt Mackall" <mpm@selenic.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: IRQF_SAMPLE_RANDOM question...
Date: Tue, 7 Apr 2009 18:30:37 -0400 [thread overview]
Message-ID: <200904071830.38081.rgetz@blackfin.uclinux.org> (raw)
In-Reply-To: <a24804730904071439g4cc1779bi1ebaf814d370708c@mail.gmail.com>
On Tue 7 Apr 2009 17:39, Chris Peterson pondered:
> 1. Are there any new add_*_randomness() functions that could be added?
I can think of - USB, serial, SDIO - but if any are heavily loaded with
constant data - their randomness reduces, and becomes less useful. if it is
the normal use case - then these might be better - but it is a function of
the local users's use of the device - and is not remotely attackable.
> Some userspace daemons like EGD (running as root) feed random system
> info (e.g. vmstat) into /dev/random. But how many Linux distros
> actually run entropy-gathering daemons by default?
Not many that I can find.
> Would /dev/random
> be more secure if entropy-gathering daemons were replaced with new
> kernel functions like add_vmstat_randomness() or add_ps_randomness()?
on embedded and server - it is likely most of ps (except load) will be pretty
stable - even vmstat - might be on more stable than you think on embedded -
which starts processes, allocates memory, and then just runs forever.....
> 2. Are there any other functions that could be calling the existing
> add_*_randomness() functions? Currently:
>
> * add_input_randomness() is called from input_event().
Could be added in the serial core? usb? spi? i2c?
> * add_interrupt_randomess() is called from handle_IRQ_event() if
> IRQF_SAMPLE_RANDOM is set.
> * add_disk_randomness() is called from blk_end_io() and __blk_end_request().
next prev parent reply other threads:[~2009-04-07 22:29 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
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 [this message]
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=200904071830.38081.rgetz@blackfin.uclinux.org \
--to=rgetz@blackfin.uclinux.org \
--cc=cpeterso@cpeterso.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=netdev@vger.kernel.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).