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:   Stephan Mueller <smueller@chronox.de>
To:     Alexander Dahl <ada@thorsis.com>
Cc:     linux-crypto@vger.kernel.org
Subject: Re: jitterentropy_rng on armv5 embedded target
Date:   Fri, 08 May 2020 14:22:02 +0200
Message-ID: <8028774.qcRHhbuxM6@tauon.chronox.de>
In-Reply-To: <2049720.SxWqT2AVQ6@ada>
References: <2567555.LKkejuagh6@ada> <6309135.Bj5FvMsAKG@tauon.chronox.de> <2049720.SxWqT2AVQ6@ada>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Sender: linux-crypto-owner@vger.kernel.org
Precedence: bulk

Am Freitag, 8. Mai 2020, 14:17:25 CEST schrieb Alexander Dahl:

Hi Alexander,

> > > 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 ?

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.


Ciao
Stephan