Am Freitag, 8. Mai 2020, 14:26:41 CEST schrieb Alexander Dahl:
Hi Alexander,
> 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
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
>
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
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.)
>
Am Freitag, 8. Mai 2020, 13:40:08 CEST schrieb Alexander Dahl:
Hi Alexander,
> Hello,
>
> after upgrading OpenSSL to 1.1.1g on an armv5 based embedded target I had a
> deeper look into entropy generation for that device and stumbled over the in
> kernel 'jitterentropy_rng' module.
>
> As far as
Hello,
after upgrading OpenSSL to 1.1.1g on an armv5 based embedded target I had a
deeper look into entropy generation for that device and stumbled over the in
kernel 'jitterentropy_rng' module.
As far as I understood it's supposed to do the same as the well known
'haveged' or the userspace da
