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: <d92d049a-8810-a765-d57a-2a7a805fadaf@gmail.com> Date: Wed, 25 Apr 2018 21:11:08 -0700 From: Sultan Alsawaf <sultanxda@...il.com> To: linux-kernel@...r.kernel.org Cc: tytso@....edu Subject: Re: Linux messages full of `random: get_random_u32 called from` 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. Detailed information on my system can be found on this bug report I recently worked on: https://bugzilla.kernel.org/show_bug.cgi?id=199463
Powered by blists - more mailing lists