From: Alexander Dahl <ada@thorsis.com>
To: linux-crypto@vger.kernel.org
Cc: Stephan Mueller <smueller@chronox.de>
Subject: Re: jitterentropy_rng on armv5 embedded target
Date: Fri, 08 May 2020 14:17:25 +0200 [thread overview]
Message-ID: <2049720.SxWqT2AVQ6@ada> (raw)
In-Reply-To: <6309135.Bj5FvMsAKG@tauon.chronox.de>
Hello, Stephan,
Am Freitag, 8. Mai 2020, 13:58:14 CEST schrieb Stephan Mueller:
> > (Although those daemons would solve my problem, I currently try
> > to avoid them, because memory on my platform is very restricted and every
> > additional running userspace process costs at least around 1 MB.)
>
> If you compile it and you also have AF_ALG for RNGs compiled, you can use it
> through the AF_ALG interface (see [1] for a library). But IMHO if you are
> space-constrained, you do not want that code.
>
> Rather use the jitterentropy-library from [2] and link it straight from your
> application.
That would be dropbear or openssl (and applications using libssl). While that
would certainly be nice, I fear it's out of my scope. ;-)
> > If so, then how is it supposed to be set up?
>
> It is intended for in-kernel purposes (namely to seed its DRBG).
Okay and DRBG has nothing to do with /dev/random ? Then where do the random
numbers for that come from (in the current or previous kernels without your
new lrng)?
Curious
Alex
next prev parent reply other threads:[~2020-05-08 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-08 11:40 jitterentropy_rng on armv5 embedded target Alexander Dahl
2020-05-08 11:58 ` Stephan Mueller
2020-05-08 12:17 ` Alexander Dahl [this message]
2020-05-08 12:22 ` Stephan Mueller
2020-05-08 12:26 ` Alexander Dahl
2020-05-08 12:30 ` Stephan Mueller
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=2049720.SxWqT2AVQ6@ada \
--to=ada@thorsis.com \
--cc=linux-crypto@vger.kernel.org \
--cc=smueller@chronox.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