From: Ken Goldman <kgold@linux.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
Sughosh Ganu <sughosh.ganu@linaro.org>
Cc: linux-integrity@vger.kernel.org
Subject: Re: Seal/Unseal trusted keys against PCR policy
Date: Fri, 6 Jan 2023 16:52:24 -0500 [thread overview]
Message-ID: <63a8c022-1407-d701-e756-070e299b5803@linux.ibm.com> (raw)
In-Reply-To: <2910376b6912885f696afebf43b820513c004dbb.camel@HansenPartnership.com>
On 12/28/2022 5:48 PM, James Bottomley wrote:
> The main thing you have to do is connect to the TPM not through the
> resource manager so the policy session survives multiple commands
>
> export TPM_DEVICE=/dev/tpm0
Just FYI, as James says, command line utilities interact with the
resource manager. When I want to run command line programs through the
resource manager, I use a proxy to keep the /dev/tpmrm0 session connected.
https://github.com/kgoldman/ibmtss/blob/master/utils/tpmproxy.c holds an
open source proxy.
next prev parent reply other threads:[~2023-01-06 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 4:14 Seal/Unseal trusted keys against PCR policy Sughosh Ganu
2022-12-27 15:40 ` James Bottomley
2022-12-28 20:40 ` Sughosh Ganu
2022-12-28 22:48 ` James Bottomley
2022-12-29 8:42 ` Sughosh Ganu
2023-01-06 21:52 ` Ken Goldman [this message]
2023-01-06 22:23 ` William Roberts
2023-01-06 23:07 ` James Bottomley
[not found] ` <CAFftDdrnoc7zsxqLGuGDVK9fh1xh3E3dT2+9rKm7BPr114ZjFA@mail.gmail.com>
2023-01-11 12:19 ` Sughosh Ganu
2023-01-11 12:31 ` James Bottomley
2023-01-11 13:50 ` William Roberts
2023-01-11 14:42 ` James Bottomley
2023-01-06 23:17 ` Ken Goldman
2023-01-07 0:38 ` William Roberts
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=63a8c022-1407-d701-e756-070e299b5803@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-integrity@vger.kernel.org \
--cc=sughosh.ganu@linaro.org \
/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