Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
Message-ID: <2904279.2zIEgBPu8l@ada>
In-Reply-To: <8028774.qcRHhbuxM6@tauon.chronox.de>
References: <2567555.LKkejuagh6@ada> <2049720.SxWqT2AVQ6@ada> <8028774.qcRHhbuxM6@tauon.chronox.de>
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

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