Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751479AbdFCAU3 (ORCPT ); Fri, 2 Jun 2017 20:20:29 -0400 Received: from mail-wr0-f172.google.com ([209.85.128.172]:36855 "EHLO mail-wr0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750971AbdFCAU2 (ORCPT ); Fri, 2 Jun 2017 20:20:28 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170602172616.47qcxav6adq52nmk@thunk.org> <20170602190734.6zll7zc5hr66oacl@thunk.org> From: Sandy Harris Date: Fri, 2 Jun 2017 20:20:26 -0400 Message-ID: Subject: Re: [kernel-hardening] Re: get_random_bytes returns bad randomness before seeding is complete To: "Jason A. Donenfeld" Cc: "Theodore Ts'o" , Stephan Mueller , Linux Crypto Mailing List , LKML , kernel-hardening@lists.openwall.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 817 Lines: 15 The only sensible & general solution for the initialisation problem that I have seen is John Denker's. http://www.av8n.com/computer/htm/secure-random.htm#sec-boot-image If I read that right, it would require only minor kernel changes & none to the API Ted & others are worrying about. It would be secure except against an enemy who can read your kernel image or interfere with your install process. Assuming permissions are set sensibly, that means an enemy who already has root & such an enemy has lots of much easier ways to break things, so we need not worry about that case. The difficulty is that it would require significant changes to installation scripts. Still, since it is a general solution to a real problem, it might be better to implement that rather than work on the other suggestions in the thread.