From: Pavel Machek <pavel@ucw.cz>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Matt Mackall <mpm@selenic.com>, Michael Buesch <mb@bu3sch.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC #2] hwrng: Add type categories
Date: Sun, 8 Jul 2007 12:53:32 +0000 [thread overview]
Message-ID: <20070708125332.GA4229@ucw.cz> (raw)
In-Reply-To: <20070627024856.GB5491@khazad-dum.debian.net>
Hi!
> Instead of papering over the problem with borked solutions, maybe we should
> just export ALL HRNGs to userspace. While at it, please add whatever is
> needed so that userspace can talk to the kernel driver to get vital
> information about the HRNG device the driver might have (the current
> interface is a bad simplistic hack).
>
> Let userspace get the data from whichever HRNG it wants, process it in any
> way it wants and pipe it back through /dev/random IOCTLs. And let it do it
> for as many HRNGs it wants at the same time.
Hmm.... xor all available HRNGs together? That way you have random
data if you have at least one goot HRNG in your system :-).
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-07-08 13:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-26 18:21 [PATCH RFC #2] hwrng: Add type categories Michael Buesch
2007-06-26 22:45 ` Matt Mackall
2007-06-27 2:40 ` Matt Mackall
2007-06-27 2:48 ` Henrique de Moraes Holschuh
2007-06-27 13:05 ` Michael Buesch
2007-06-27 13:10 ` Michael Buesch
2007-06-27 17:03 ` Henrique de Moraes Holschuh
2007-06-27 17:54 ` Michael Buesch
2007-06-28 8:07 ` Henrique de Moraes Holschuh
2007-07-08 12:53 ` Pavel Machek [this message]
2007-06-27 12:57 ` Michael Buesch
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=20070708125332.GA4229@ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=hmh@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=mpm@selenic.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