lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180426050056.GF18803@thunk.org> Date: Thu, 26 Apr 2018 01:00:56 -0400 From: "Theodore Y. Ts'o" <tytso@....edu> To: Sultan Alsawaf <sultanxda@...il.com> Cc: linux-kernel@...r.kernel.org, Jann Horn <jannh@...gle.com> Subject: Re: Linux messages full of `random: get_random_u32 called from` On Wed, Apr 25, 2018 at 09:11:08PM -0700, Sultan Alsawaf wrote: > I noticed "systems without sufficient boot randomness" and would like to add to this. > > With the changes to /dev/random going from 4.16.3 to 4.16.4, my low-spec Chromebook does not reach > the login screen upon boot (it stays stuck on a black screen) until I provide a source of entropy to > the system via interrupts (e.g., holding down a key on the keyboard for 5 sec or moving my finger > across the touchpad a lot). After providing a source of entropy for long enough, > "random: crng init done" prints out in dmesg and the login screen finally pops up. Thanks for the report! I assume since you're upgrading your own kernel, you must not be running Chrome OS on your Acer CB3-431 Chromebook (Edgar). Are you running Chromium --- or some Linux distribution on it? Thanks, - Ted
Powered by blists - more mailing lists