[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080515233642.GT18825@mit.edu>
Date: Thu, 15 May 2008 19:36:42 -0400
From: Theodore Tso <tytso@....edu>
To: Henrique de Moraes Holschuh <hmh@....eng.br>
Cc: Jeff Garzik <jeff@...zik.org>,
Chris Peterson <cpeterso@...terso.com>,
"Kok, Auke" <auke-jan.h.kok@...el.com>,
Rick Jones <rick.jones2@...com>,
"Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
Alan Cox <alan@...rguk.ukuu.org.uk>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drivers/net: remove network drivers' last few uses of
IRQF_SAMPLE_RANDOM
On Thu, May 15, 2008 at 08:02:21PM -0300, Henrique de Moraes Holschuh wrote:
> 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.
There were some web pages on this subject that seemed imply that IBM
used a non-standard string-to-key algorithm, and that caused the
incompatibility with Trousers. So if you initialized the TPM using
the IBM Windows drivers, you have to mess around with TSS to get it to
work correctly with Thinkpads. I tried for a bit to try to get it to
work a while ago, but the few things I tried didn't work, and I
eventually lost interest.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists