Removing the Linux /dev/random blocking pool

Posted Jan 8, 2020 7:40 UTC (Wed) by joib (subscriber, #8541)
Parent article: Removing the Linux /dev/random blocking pool

How does this all now work with the jitter RNG that was recently introduced?

So this change makes /dev/random work mostly like getrandom(0). If there's not enough entropy, they will block until enough entropy has been generated (including by running the jitter RNG) to seed the CRNG? After the CRNG has been seeded, they never block.

What about /dev/urandom? It will never block (including not kicking the jitter RNG into action?), so it will seed the CRNG with whatever entropy there is? This is the same as getrandom() with the new GRND_INSECURE flag? And then presumably some protection against state extension attacks?