From: "Stephan Müller" <smueller@chronox.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Matt Mackall <mpm@selenic.com>
Subject: Re: Question - seeding the hw pseudo random number generator
Date: Sun, 26 Mar 2017 06:10:44 +0200 [thread overview]
Message-ID: <1882318.c2IBOhq8iD@positron.chronox.de> (raw)
In-Reply-To: <20170323094406.GA6848@gondor.apana.org.au>
Am Donnerstag, 23. März 2017, 10:44:06 CEST schrieb Herbert Xu:
Hi Herbert,
> On Thu, Mar 23, 2017 at 09:23:07AM +0100, Corentin Labbe wrote:
> > Problem with this conversion, a huge regression for user space.
> > Using hwrng is simple as cat /dev/hwrng.
> > Using algif_rng via AF_ALG is ... unusable for the moment.
> > Perhaps creating an user space tool (prng-tool which provide a cat
> > /dev/hwrng replacement) is mandatory before any convertion.
> Stephan may have a tool to do this. Stephan?
I added the application kcapi-rng to HEAD of [1]. Create the application with
the --enable-kcapi-rngapp configure option.
$ kcapi-rng
Kernel Crypto API Random Number Gatherer
Kernel Crypto API interface library version: libkcapi pre-release 0.13.1
Reported numeric version number 130080
Usage:
-b --bytes <BYTES> Number of bytes to generate (required option)
-h --help This help information
--version Print version
-v --verbose Verbose logging, multiple options increase verbosity
Data provided at stdin is used to seed the DRNG
[1] https://github.com/smuellerDD/libkcapi/
Ciao
Stephan
prev parent reply other threads:[~2017-03-26 4:10 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
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 [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=1882318.c2IBOhq8iD@positron.chronox.de \
--to=smueller@chronox.de \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--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