From: "H. Peter Anvin" <hpa@zytor.com>
To: Kent Yoder <key@linux.vnet.ibm.com>
Cc: James Morris <jmorris@namei.org>,
Peter Huewe <peter.huewe@infineon.com>,
Bryan Freed <bfreed@chromium.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org
Subject: Re: [GIT PULL] New TPM driver and features
Date: Fri, 27 Jul 2012 08:08:28 -0700 [thread overview]
Message-ID: <5012AEEC.4040400@zytor.com> (raw)
In-Reply-To: <20120727142921.GA28347@linux.vnet.ibm.com>
On 07/27/2012 07:29 AM, Kent Yoder wrote:
> Hi,
>
> On Thu, Jul 26, 2012 at 02:46:25PM -0700, H. Peter Anvin wrote:
>> On 07/26/2012 07:31 AM, Kent Yoder wrote:
>>> hw_random: add support for the TPM chip as a hardware RNG source
>>
>> Could you clarify this? rngd (the user of /dev/hw_random) already
>> has support for the TPM... is this fundamentally different (e.g. can
>> it coexist with tcsd being in use at the same time)?
>
> These can coexist at the same time since /dev/tpm0 is only opened once
> from user-space (from tcsd) and this hwrng driver comes in through the
> kernel. There would be some amount of contention with the tpm, but its
> not likely to be noticable - grabbing rng data doesn't require any state
> in the tpm, like an auth session or key loading.
>
> Since the rngd support for the tpm requires trousers, this patch will
> be useful in places where you don't want to have to deploy the full TSS,
> like embedded and early boot.
>
Actually the rngd support for the TPM *conflicts* with trousers... I was
looking at adding trousers support when I stumbled over your patch.
Your patch is better, because it solves the handover problem (rngd
should normally be started as early as possible.)
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
prev parent reply other threads:[~2012-07-27 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 14:31 [GIT PULL] New TPM driver and features Kent Yoder
2012-07-26 21:46 ` H. Peter Anvin
2012-07-27 14:29 ` Kent Yoder
2012-07-27 15:08 ` H. Peter Anvin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5012AEEC.4040400@zytor.com \
--to=hpa@zytor.com \
--cc=bfreed@chromium.org \
--cc=jmorris@namei.org \
--cc=key@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=peter.huewe@infineon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox