[onerng talk] /dev/random/urandom question - wireguard related

[Paul Campbell]

On Wednesday, 22 July 2020 8:09:07 AM NZST alexandre wrote:
> if not wrong the onerng script only feed /dev/random by default,

There's a new issue with the kernel drivers for /dev/random and /dev/urandom - 
the kernel devs have very recently changed things so that /dev/random no 
longer works the way it used to and rngd (the standard mechanism that OneRNG 
uses to feed /dev/random) no longer feeds the kernel entropy pool.

You can still use OneRNG directly to get random data directly

/dev/urandom in the past used to be a mechanism to access an entropy pool that 
was initialised at system startup time, now it and /dev/random essentially 
work the same way (previously /dev/urandom was updated periodically with 
OneRNG data every few seconds but another kernel changes broke that too)

I'm going to release new OneRNG system software soon that hopefully solves 
this problem (and the python3 problem) as soon as possible

	Paul Campbell