From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: bug#36380: service urandom-seed takes too long on boot Date: Sun, 22 Mar 2020 16:19:19 -0400 Message-ID: <20200322201919.GC16716@jasmine.lan> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37813) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jG74k-000116-W8 for bug-guix@gnu.org; Sun, 22 Mar 2020 16:20:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jG74j-00050d-VK for bug-guix@gnu.org; Sun, 22 Mar 2020 16:20:02 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:44980) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jG74j-00050R-Q7 for bug-guix@gnu.org; Sun, 22 Mar 2020 16:20:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jG74j-0004V9-MK for bug-guix@gnu.org; Sun, 22 Mar 2020 16:20:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: Content-Disposition: inline In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Brice Waegeneire Cc: 36380@debbugs.gnu.org On Sun, Mar 22, 2020 at 08:43:33AM +0000, Brice Waegeneire wrote: > This article has been updated since then with a section[0] about a fix > authored by Linus[1][2] and merged in Linux 5.4. The gist of it that now > `getrandom()' will actively try to collect entropy in early boot, if it > is missing, by using the CPU jitter. The Debian wiki is saying the same[3]. The issue here is not related to getrandom() or our kernel. I think the bug is still relevant. The Guix system unconditionally reads from /dev/hwrng if it exists, and there is no reason for that to take a noticeable amount of time. But this bug report revealed that some VPS providers have a broken deployment that does cause delays. Who knows how they are feeding /dev/hwrng... they would not reply to my questions. It doesn't really matter though, the problem is ours to fix. We need to make this read time out after a second, but in the past I could not figure out how to do this without crashing the system (I'm not a strong Schemer). Help is still wanted!