Random warnings on TOS4

Software Turris OS 4.x
1 
[    6.508803] random: fast init done
[    9.188468] random: jshn: uninitialized urandom read (4 bytes read)
[    9.204723] random: jshn: uninitialized urandom read (4 bytes read)
[    9.219385] random: jshn: uninitialized urandom read (4 bytes read)
[   12.865649] urandom_read: 2 callbacks suppressed
[   12.865652] random: procd: uninitialized urandom read (4 bytes read)
[   13.056906] urandom-seed: Seeding with /etc/urandom.seed
[   13.698772] random: ubusd: uninitialized urandom read (4 bytes read)
[   13.744295] random: ubusd: uninitialized urandom read (4 bytes read)
[   16.794904] random: crng init done
[   16.798318] random: 2 urandom warning(s) missed due to ratelimiting

Is it because haveged is starting too late?

2

urnadom provides an interface to the kernel’s random number generator and starts earlier than haveged.

urandom - The random number generator gathers environmental noise from device drivers and other sources into an entropy pool

haveged - is an attempt to provide an easy-to-use, unpredictable random number generator based upon an adaptation of the HAVEGE algorithm

Different methodology.

The warning is expected since there is not much environmental noise available that earlier in the boot process.

3

Right but notice that the warnings come from userspace programs (jshn, procd, and ubusd). OpenWrt’s alternative to haveged starts at 00 instead of 13 according to the init script.

4

Curiously though OpenWRT’s description of haveged differs

Feeds the kernel entropy pool by timing CPU loops.

I am not sure how many CPU loops are available that early in boot process and whether it would make a difference of haveged’s entropy produce at that stage compared to urandom’s.

Since this is a user forum you could also lodge an issue with the developers