From mboxrd@z Thu Jan 1 00:00:00 1970 From: Henrique de Moraes Holschuh Subject: Re: [PATCH] drivers/net: remove network drivers' last few uses of IRQF_SAMPLE_RANDOM Date: Thu, 15 May 2008 20:58:38 -0300 Message-ID: <20080515235838.GB23721@khazad-dum.debian.net> References: <482C7E53.3050300@hp.com> <482C8184.2030906@garzik.org> <482C8550.5000909@intel.com> <482C8D4D.3040702@garzik.org> <20080515214721.GP18825@mit.edu> <482CB1FB.7080807@garzik.org> <20080515222941.GB20976@khazad-dum.debian.net> <482CBCC6.6010905@garzik.org> <20080515233305.GS18825@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Theodore Tso , Jeff Garzik , Chris Peterson , "Kok, Auke" , Rick Jones , "Brandeb Return-path: Received: from out1.smtp.messagingengine.com ([66.111.4.25]:48683 "EHLO out1.smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754793AbYEOX6l (ORCPT ); Thu, 15 May 2008 19:58:41 -0400 Content-Disposition: inline In-Reply-To: <20080515233305.GS18825@mit.edu> Sender: netdev-owner@vger.kernel.org List-ID: On Thu, 15 May 2008, Theodore Tso wrote: > On Thu, May 15, 2008 at 06:44:22PM -0400, Jeff Garzik wrote: > > I just sorta assumed a buffering, interrupt-driver TPM RNG driver would be > > better than doing it from userspace, but maybe that was a bad assumption to > > make on my part. It should be quite doable to support TPM RNG entirely via > > userspace, at any rate. > > If I recall correctly, you need access to a magic TPM key just to > *talk* to the TPM. Normally that key is stored in a file, and of The TPM has some sort of idea of restricted operations. It will depend whether one can get random numbers as an anonymous party (and frankly, I don't care for looking at the TCG docs right now to find out). I certaily can ask the TPM "are you there?" even when it is disabled(!), so I would not be too surprised to find out that, as long as it is enabled, it will return random numbers to anyone. But access to the TPM requires a control layer which must have excusive access to the chip. That layer would have to move into the kernel... IMHO, it is just not worth even bothering with the idea, and just do it all in userspace. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh