News for hackers. Stuff that matters.

A comment on Fixing Getrandom(). Parent comment

Re:Fixing Getrandom() by bonzini on Tuesday October 01, 2019 @03:43PM (#21129716)
This is happening so early that audio and network (and /var where the persistent seed is stored) aren't up. The kernel doesn't want to be susceptible to hangs unless userspace brings up all entropy sources early enough.
[ Parent | on HN ]
Re:Fixing Getrandom() by nwallin on Tuesday October 01, 2019 @05:55PM (#21131154)
This is about GDM, which is the last thing that gets started.

Hardware devices are initialized before init is started, so you should still be able to gather entropy from the various input devices.

Lack of entropy can't cause the kernel to not boot; it's just userspace (typically services which require encryption) which can have a problem. It would be silly to start a webserver or sshd before the FS is remounted rw.

[ Parent | on HN ]
Re:Fixing Getrandom() by megous on Tuesday October 01, 2019 @09:29PM (#21132688)
Not if you use modules.
[ Parent | on HN ]
Re:Fixing Getrandom() by loeg on Wednesday October 02, 2019 @04:16AM (#21134321)
Can you elaborate on what you mean?
[ Parent | on HN ]
Re:Fixing Getrandom() by megous on Wednesday October 02, 2019 @06:41AM (#21134978)
Init is executed before modules start being loaded.
[ Parent | on HN ]
Re:Fixing Getrandom() by the8472 on Tuesday October 01, 2019 @05:45PM (#21131050)
The issue was GDM/X11 starting though, that's later into the boot sequence.
[ Parent | on HN ]