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:26:41 +0200 [thread overview]
Message-ID: <2904279.2zIEgBPu8l@ada> (raw)
In-Reply-To: <8028774.qcRHhbuxM6@tauon.chronox.de>
Hello,
Am Freitag, 8. Mai 2020, 14:22:02 CEST schrieb Stephan Mueller:
> Am Freitag, 8. Mai 2020, 14:17:25 CEST schrieb Alexander Dahl:
> > Okay and DRBG has nothing to do with /dev/random ?
>
> Nope, it is used as part of the kernel crypto API and its use cases.
>
> > Then where do the random
> > numbers for that come from (in the current or previous kernels without
> > your
> > new lrng)?
>
> The DRBG is seeded from get_random_bytes and the Jitter RNG.
Oh, I was not precise enough. I wanted to know where /dev/random gets its
numbers from. As far as I understood now: not from DRBG? (Which is sufficient
knowledge for my current problem.)
Greets
Alex
next prev parent reply other threads:[~2020-05-08 12:26 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
2020-05-08 12:22 ` Stephan Mueller
2020-05-08 12:26 ` Alexander Dahl [this message]
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=2904279.2zIEgBPu8l@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.