From: Jeff Garzik <jeff@garzik.org>
To: Michael Buesch <mb@bu3sch.de>
Cc: moreau francis <francis_moreau2000@yahoo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: [HW_RNG] How to use generic rng in kernel space
Date: Fri, 04 Aug 2006 21:44:01 -0400 [thread overview]
Message-ID: <44D3F7E1.4030703@garzik.org> (raw)
In-Reply-To: <200608042308.24421.mb@bu3sch.de>
Michael Buesch wrote:
> I am not a friend of a direct in-kernel hwrng access interface,
> because it may return crap data by definition. Many (all current)
> RNG devices may fail and return non-random data. If that's happily
> used by some in-kernel user by the interface, we are screwed.
Yes, this is the reason why we pass it through userspace...
Jeff
next prev parent reply other threads:[~2006-08-05 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 12:09 [HW_RNG] How to use generic rng in kernel space moreau francis
2006-08-01 13:29 ` Alan Cox
2006-08-01 13:28 ` Re : " moreau francis
2006-08-01 20:49 ` Michael Buesch
2006-08-04 13:00 ` Re : " moreau francis
2006-08-04 21:08 ` Michael Buesch
2006-08-05 1:44 ` Jeff Garzik [this message]
2006-08-08 15:39 ` Re : " moreau francis
2006-08-08 17:34 ` Michael Buesch
2006-08-09 10:02 ` Re : " moreau francis
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=44D3F7E1.4030703@garzik.org \
--to=jeff@garzik.org \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
/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