On Mon, May 07, 2018 at 02:58:03PM +1200, Ben Caradoc-Davies wrote:
> This reverts commit 43838a23a05f ("random: fix crng_ready() test"),
> which causes urandom to hang in early boot even when crng_init==1.
>
> One impact of this hang is that it prevents display of the plymouth
> graphical
By the way, if anyone is interested in working on this related
problem:
https://news.ycombinator.com/item?id=16976421
The reason why this is hard is because Linux is supported on a
great number of architectures, and some architectures have more
than one boot loader that is used. The
On 07/05/18 15:29, Theodore Y. Ts'o wrote:
Unfortunately, commit 43838a23a05f is needed to address CVE-2018-1108,
which was reported by Jann Horn of Google's Project Zero. There are
real problems with allowing programs to assume that they have a fully
initialized cryptographic random number
This reverts commit 43838a23a05f ("random: fix crng_ready() test"),
which causes urandom to hang in early boot even when crng_init==1.
One impact of this hang is that it prevents display of the plymouth
graphical passphrase prompt required to proceed with boot. In the
absence of sources of
4 matches
Mail list logo
