From: Ken Goldman <kgold@linux.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH 6/8] security: keys: trusted: add PCR policy to TPM2 keys
Date: Wed, 25 Dec 2019 12:08:47 -0500 [thread overview]
Message-ID: <f3e2e163-1754-1360-1454-70391aed8b95@linux.ibm.com> (raw)
In-Reply-To: <1575918695.31378.18.camel@HansenPartnership.com>
On 12/9/2019 2:11 PM, James Bottomley wrote:
> Plus, I know of no policy statement that's anywhere near 127 bytes
> long, so there's no problem with doing the single byte fixed length
> that DER requires.
Is "a policy statement" the TPM command?
PolicyOr takes a list of hashes. A typical policy may only have 3
sha256 hashes, but it could potentially be 8 sha384 hashes.
PolicySigned has a policy with a 256 byte public key and a TPM
command with a 256 byte signature.
In general, since the TPM input command buffer is 1 - 1.5k,
that's a reasonable value for input parameters.
next prev parent reply other threads:[~2019-12-25 17:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-08 5:06 [PATCH 0/8] Fix TPM 2.0 trusted keys James Bottomley
2019-12-08 5:07 ` [PATCH 1/8] security: keys: trusted: flush the key handle after use James Bottomley
2019-12-09 8:31 ` David Woodhouse
2019-12-09 15:38 ` James Bottomley
2019-12-08 5:08 ` [PATCH 2/8] lib: add asn.1 encoder James Bottomley
2019-12-09 8:50 ` David Woodhouse
2019-12-09 15:46 ` James Bottomley
2019-12-09 22:05 ` Matthew Garrett
2019-12-09 22:43 ` James Bottomley
2019-12-08 5:09 ` [PATCH 3/8] oid_registry: Add TCG defined OIDS for TPM keys James Bottomley
2019-12-09 8:55 ` David Woodhouse
2019-12-09 16:21 ` James Bottomley
2020-06-19 20:45 ` Wiseman, Monty (GE Research, US)
2020-06-19 22:50 ` Jerry Snitselaar
2020-06-20 15:36 ` James Bottomley
2020-06-23 1:17 ` Jarkko Sakkinen
2019-12-08 5:10 ` [PATCH 4/8] security: keys: trusted: use ASN.1 tpm2 key format for the blobs James Bottomley
2019-12-09 10:04 ` David Woodhouse
2019-12-09 16:31 ` James Bottomley
2019-12-08 5:11 ` [PATCH 5/8] security: keys: trusted: Make sealed key properly interoperable James Bottomley
2019-12-09 10:09 ` David Woodhouse
2019-12-09 17:23 ` James Bottomley
2019-12-08 5:12 ` [PATCH 6/8] security: keys: trusted: add PCR policy to TPM2 keys James Bottomley
2019-12-09 10:18 ` David Woodhouse
2019-12-09 18:03 ` James Bottomley
2019-12-09 18:44 ` David Woodhouse
2019-12-09 19:11 ` James Bottomley
2019-12-25 17:08 ` Ken Goldman [this message]
2019-12-08 5:13 ` [PATCH 7/8] security: keys: trusted: add ability to specify arbitrary policy James Bottomley
2019-12-08 5:14 ` [PATCH 8/8] security: keys: trusted: implement counter/timer policy James Bottomley
2019-12-09 20:20 ` [PATCH 0/8] Fix TPM 2.0 trusted keys Jarkko Sakkinen
2019-12-09 20:57 ` James Bottomley
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=f3e2e163-1754-1360-1454-70391aed8b95@linux.ibm.com \
--to=kgold@linux.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-integrity@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.