Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756900Ab3IKTIq (ORCPT ); Wed, 11 Sep 2013 15:08:46 -0400 Received: from mail-vb0-f43.google.com ([209.85.212.43]:38188 "EHLO mail-vb0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751460Ab3IKTIp (ORCPT ); Wed, 11 Sep 2013 15:08:45 -0400 MIME-Version: 1.0 In-Reply-To: References: <1378920168.26698.64.camel@localhost> <20130911184509.GB13397@thunk.org> From: Andy Lutomirski Date: Wed, 11 Sep 2013 12:08:24 -0700 Message-ID: Subject: Re: TPMs and random numbers To: Jeff Garzik Cc: "Theodore Ts'o" , David Safford , "H. Peter Anvin" , Leonidas Da Silva Barbosa , Ashley Lai , Rajiv Andrade , Marcel Selhorst , Sirrix AG , Linux Kernel Mailing List , Kent Yoder , David Safford , Mimi Zohar , "Johnston, DJ" Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 24 On Wed, Sep 11, 2013 at 12:06 PM, Jeff Garzik wrote: > On Wed, Sep 11, 2013 at 2:45 PM, Theodore Ts'o wrote: >> We should definitely do this. If the TPM driver could fetch some >> randomness and then call add_device_randomness() to feed this into the >> random driver's entropy pool when it initializes itself, that would be >> ***really*** cool. > > > rngd already does this. And all those random numbers generated before rngd starts are quite possibly crap. I think that rngd makes sense as a tool to access strange sources of entropy and to periodically reseed the pool, but I also think that the kernel should really be pulling in easily available entropy on its own at startup. --Andy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/