Received: by 10.192.165.148 with SMTP id m20csp3175623imm; Sun, 29 Apr 2018 16:07:56 -0700 (PDT) X-Google-Smtp-Source: AB8JxZrt0w44YnvKZyK9mNcNawsUOVvlDOmtlIHyJuc1gYgooxDJcL7W5z7pvM8mbyPBBslB2bFl X-Received: by 2002:a17:902:a5c7:: with SMTP id t7-v6mr2127158plq.360.1525043276689; Sun, 29 Apr 2018 16:07:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525043276; cv=none; d=google.com; s=arc-20160816; b=OTUNEczxnM2EwIqWE59uYM3yA/bLM0ltGNaqf5qxQNBmxEgHYJXpoYWMDMWgwSEpB1 /egBZpD8oqBKDgfwqs4kQ3zG9QqmEVrUjnBe89Bq8jKKzaOuCdVAowagIwf3SfWrvHxT nhCMMg3S0syN+MZ+9O9Apar1vaYsZfoEzTUwLtOq1axLRF/NooY//K6IIdyD/MBK/x5I 490WwTIjzJHdc+F5B3dgxPrrw5e/FOXMrlzNIhH3lg6ELN9UW1cKcN5aYeSyOwsa8xoM aa96ZghwLaZMQoQxsN+/wCij8hMlyaG9pyNMRXeHs+vWCSzwogbIzAw1ACjhkf7zE0kH X87g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:mail-followup-to :message-id:subject:to:from:date:arc-authentication-results; bh=f9Sjl2tPsgDpWxAlepyqAvXYzfRhTEf9wL2Dqc9sk1Q=; b=f2lAZHBfQURVlN+renPxgWkJnD3fbYg9VvQU4GL4rF+etgJxCEO/N+aafKkK4ymJUm OUvZjvi2hHjf3kJi2h8pEPq2GHpiqQpIgdIpWgp1v7aTubB2PM+OqcRi5iSqhCuXBHNa zjL83srXst6QLNbvv85FPIf5UDPwfd1bQiizYt043i4XIyng5IZLWGzFeRpeAo0QXXMc U2V9H5Hplcza+do+pBGDJZKDOXz+iejm9/WC/S1Ig6dv7caMdPMpuMgOBzt/7Z123eO9 Oi4e7KJYENX7vLE54ZOVPmUmJZCweiDSOwTSpiOfvsXLux+N3AOHjFARUGMeJQ5UY12V 4Rpg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b89-v6si6328344plb.262.2018.04.29.16.07.43; Sun, 29 Apr 2018 16:07:56 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754524AbeD2XHc (ORCPT + 99 others); Sun, 29 Apr 2018 19:07:32 -0400 Received: from scorn.kernelslacker.org ([45.56.101.199]:59932 "EHLO scorn.kernelslacker.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754352AbeD2XHb (ORCPT ); Sun, 29 Apr 2018 19:07:31 -0400 Received: from [2601:196:4600:5b90:ae9e:17ff:feb7:72ca] (helo=wopr.kernelslacker.org) by scorn.kernelslacker.org with esmtp (Exim 4.89) (envelope-from ) id 1fCvPl-0003nq-8f; Sun, 29 Apr 2018 19:07:29 -0400 Received: by wopr.kernelslacker.org (Postfix, from userid 1026) id 112FF560060; Sun, 29 Apr 2018 19:07:29 -0400 (EDT) Date: Sun, 29 Apr 2018 19:07:29 -0400 From: Dave Jones To: "Theodore Y. Ts'o" , Paul Menzel , linux-kernel@vger.kernel.org Subject: Re: Linux messages full of `random: get_random_u32 called from` Message-ID: <20180429230728.whjg3fpeunxuvkyn@codemonkey.org.uk> Mail-Followup-To: Dave Jones , "Theodore Y. Ts'o" , Paul Menzel , linux-kernel@vger.kernel.org References: <42c1b84b-ab1f-5577-6304-e0985a637cf9@molgen.mpg.de> <20180424135621.GD4189@thunk.org> <20180429230202.rcsjtnp2jhbqyag2@codemonkey.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180429230202.rcsjtnp2jhbqyag2@codemonkey.org.uk> User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Note: SpamAssassin invocation failed Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Apr 29, 2018 at 07:02:02PM -0400, Dave Jones wrote: > On Tue, Apr 24, 2018 at 09:56:21AM -0400, Theodore Y. Ts'o wrote: > > > Can you tell me a bit about your system? What distribution, what > > hardware is present in your sytsem (what architecture, what > > peripherals are attached, etc.)? > > > > There's a reason why we made this --- we were declaring the random > > number pool to be fully intialized before it really was, and that was > > a potential security concern. It's not as bad as the weakness > > discovered by Nadia Heninger in 2012. (See https://factorable.net for > > more details.) However, this is not one of those things where we like > > to fool around. > > > > So I want to understand if this is an issue with a particular hardware > > configuration, or whether it's just a badly designed Linux init system > > or embedded setup, or something else. After all, you wouldn't want > > the NSA spying on all of your network traffic, would you? :-) > > Why do we continue to print this stuff out when crng_init=1 though ? answering my own question, I think.. This is a tristate, and we need it to be >1 to be quiet, which doesn't happen until.. > [ 165.806247] random: crng init done this point. Dave