On 04/12/2023 12:06, Benjamin Beichler wrote:
Am 01.12.2023 um 19:35 schrieb Johannes Berg:
[I guess we should keep the CCs so other see it]
Looking at the stuck check it will be bogus in simulations.
True.
You might as well ifdef that instead.
If a simulation is running insert the ent
Am 01.12.2023 um 19:35 schrieb Johannes Berg:
[I guess we should keep the CCs so other see it]
Looking at the stuck check it will be bogus in simulations.
True.
You might as well ifdef that instead.
If a simulation is running insert the entropy regardless and do not compute the
derivative
Am Montag, 4. Dezember 2023, 11:24:25 CET schrieb Johannes Berg:
Hi Johannes,
>
> Well it _looks_ like it might be possible to get rid of it (see above),
> however, what I was really thinking is that jitter RNG might detect that
> it doesn't actually get any reasonable data and eventually give u
Hi Stephan,
> The reason for the Jitter RNG to be dragged in is the Kconfig select in
> CRYPTO_DRBG.
Yes, but you can't get rid of DRBG either. That'd require getting rid of
CRYPTO_RNG_DEFAULT, which means you cannot even have CRYPTO_GENIV?
Hmm. Maybe it _is_ possible to get rid of all these.
Am Freitag, 1. Dezember 2023, 19:35:11 CET schrieb Johannes Berg:
Hi Johannes,
> [I guess we should keep the CCs so other see it]
>
> > Looking at the stuck check it will be bogus in simulations.
>
> True.
>
> > You might as well ifdef that instead.
> >
> > If a simulation is running insert t
