From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Matt Mackall <mpm@selenic.com>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Jan Glauber <jan.glauber@de.ibm.com>,
Harald Freudenberger <freude@de.ibm.com>
Subject: Re: Question - seeding the hw pseudo random number generator
Date: Mon, 20 Mar 2017 14:39:47 +0100 [thread overview]
Message-ID: <1509135.hmo2UhaKWe@tauon.atsec.com> (raw)
In-Reply-To: <20170320132858.GA27044@gondor.apana.org.au>
Am Montag, 20. März 2017, 14:28:58 CET schrieb Herbert Xu:
Hi Herbert,
> On Mon, Mar 20, 2017 at 12:19:32PM +0530, PrasannaKumar Muralidharan wrote:
> > AF_ALG interface for rng does have seeding support. I think hw_random
> > does not provide seeding support intentionally as I understand that
> > True RNG need not require seeding (please correct me if I am wrong).
>
> Yes. We should be converting PRNGs in hwrng over to algif_rng.
IMHO this not only applies to the PRNGs in drivers/crypto (which should simply
register with crypto_register_rngs) but also to ~/hacking/sources/linux/arch/
s390/crypto/prng.c which exports a /dev/prandom file.
For the seeding, it may make sense to follow the example given with crypto/
drbg.c using the add_random_ready_callback function.
Ciao
Stephan
next prev parent reply other threads:[~2017-03-20 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-18 9:25 Question - seeding the hw pseudo random number generator Krzysztof Kozlowski
2017-03-20 6:49 ` PrasannaKumar Muralidharan
2017-03-20 13:28 ` Herbert Xu
2017-03-20 13:39 ` Stephan Müller [this message]
2017-03-23 8:03 ` Harald Freudenberger
2017-03-23 11:35 ` Stephan Müller
2017-03-20 18:24 ` Krzysztof Kozlowski
2017-03-23 8:23 ` Corentin Labbe
2017-03-23 9:44 ` Herbert Xu
2017-03-23 11:44 ` Stephan Müller
2017-03-23 13:06 ` Stephan Müller
2017-03-26 4:10 ` Stephan Müller
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=1509135.hmo2UhaKWe@tauon.atsec.com \
--to=smueller@chronox.de \
--cc=freude@de.ibm.com \
--cc=herbert@gondor.apana.org.au \
--cc=jan.glauber@de.ibm.com \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=prasannatsmkumar@gmail.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