[lkml]   [2008]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drivers/net: remove network drivers' last few uses of IRQF_SAMPLE_RANDOM
On Thu, 15 May 2008, Jeff Garzik wrote:
> Henrique de Moraes Holschuh wrote:
>> If anyone wants to poke at it, get the Debian rng-tools source package.
>> It directly supports the VIA PadLock in userspace in a suitably paranoid
>> mode (checks that the RNG was not reprogrammed at every read), and does
>> multithreading so that FIPS and output processing does not block (nor
>> gets blocked) by /dev/hw_random reading, etc.
> Neat. I always did prefer VIA padlock in userspace.
> 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.

I will tell you what. If someone manages to get trousers to actually
*work* for data binding and sealing to the TPM in a ThinkPad T43 with an
NSC/Winbond TPM (their "sup3r s3kr1t TPM-inside-the-SuperIO 8394T" crap
one needs a NDA to get the documentation for), and I manage to duplicate
it (i.e. make it work here too), I will write the rng-tools trousers
interface code (at least for the Debian version) :-)

The kernel TPM driver works, the BIOS works, and I have the PCRs updated
properly during boot, but trousers get the tpm pubek key wrong for some
reason (the kernel driver can read it just fine). The chip is good,
IBM's stuff worked just fine with it.

"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

 \ /
  Last update: 2008-05-16 01:05    [W:0.084 / U:8.136 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site