From: Keith Packard <keithp@keithp.com>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Jason Cooper <jason@lakedaemon.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices
Date: Tue, 09 Aug 2016 16:26:30 -0700 [thread overview]
Message-ID: <86bn11r0bd.fsf@hiro.keithp.com> (raw)
In-Reply-To: <20160809201846.GA4684@khazad-dum.debian.net>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Henrique de Moraes Holschuh <hmh@hmh.eng.br> writes:
> IMHO, this is mightly annoying to use from inside a rngd-like utility in
> a race-free, safe way. It looks to me that ioctl() would be a much
> better interface for everything but the "enabled" functionality (which
> should be reported to the rngd-like utility as open() on the real device
> failing with, e.g., ENXIO, when that source is disabled).
What information does an rngd-like program actually want? All I can
think that it would need is the stream of random data. I guess some
estimate of the entropy available would be nice, but surely it would
want to verify that in any case.
--
-keith
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 810 bytes --]
prev parent reply other threads:[~2016-08-09 23:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 20:07 [PATCH] hwrng: core - Allow for multiple simultaneous active hwrng devices Keith Packard
2016-08-09 9:50 ` Herbert Xu
2016-08-09 16:57 ` Jason Cooper
2016-08-09 17:58 ` Keith Packard
2016-08-09 18:26 ` Jason Cooper
2016-08-09 19:01 ` Keith Packard
2016-08-09 20:18 ` Henrique de Moraes Holschuh
2016-08-09 23:26 ` Keith Packard [this message]
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=86bn11r0bd.fsf@hiro.keithp.com \
--to=keithp@keithp.com \
--cc=herbert@gondor.apana.org.au \
--cc=hmh@hmh.eng.br \
--cc=jason@lakedaemon.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@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