linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>,
	David Woodhouse <dwmw2@infradead.org>,
	keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>
Subject: Re: [PATCH v15 4/5] security: keys: trusted: use ASN.1 TPM2 key format for the blobs
Date: Sat, 30 Jan 2021 18:29:09 +0200	[thread overview]
Message-ID: <YBWJVcM8/2tIlWHk@kernel.org> (raw)
In-Reply-To: <20210127190617.17564-5-James.Bottomley@HansenPartnership.com>

On Wed, Jan 27, 2021 at 11:06:16AM -0800, James Bottomley wrote:
> Modify the TPM2 key format blob output to export and import in the
> ASN.1 form for TPM2 sealed object keys.  For compatibility with prior
> trusted keys, the importer will also accept two TPM2B quantities
> representing the public and private parts of the key.  However, the
> export via keyctl pipe will only output the ASN.1 format.
> 
> The benefit of the ASN.1 format is that it's a standard and thus the
> exported key can be used by userspace tools (openssl_tpm2_engine,
> openconnect and tpm2-tss-engine).  The format includes policy
> specifications, thus it gets us out of having to construct policy
> handles in userspace and the format includes the parent meaning you
> don't have to keep passing it in each time.
> 
> This patch only implements basic handling for the ASN.1 format, so
> keys with passwords but no policy.
> 
> Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
> Tested-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>

This one had some coding style errors:

WARNING: Possible repeated word: 'for'
#147: FILE: security/keys/trusted-keys/tpm2key.asn1:2:
+--- ASN.1 for for TPM 2.0 keys

ERROR: space required after that ',' (ctx:VxV)
#198: FILE: security/keys/trusted-keys/trusted_tpm2.c:29:
+static u32 tpm2key_oid[] = { 2,23,133,10,1,5 };
                               ^

ERROR: space required after that ',' (ctx:VxV)
#198: FILE: security/keys/trusted-keys/trusted_tpm2.c:29:
+static u32 tpm2key_oid[] = { 2,23,133,10,1,5 };
                                  ^

ERROR: space required after that ',' (ctx:VxV)
#198: FILE: security/keys/trusted-keys/trusted_tpm2.c:29:
+static u32 tpm2key_oid[] = { 2,23,133,10,1,5 };
                                      ^

ERROR: space required after that ',' (ctx:VxV)
#198: FILE: security/keys/trusted-keys/trusted_tpm2.c:29:
+static u32 tpm2key_oid[] = { 2,23,133,10,1,5 };
                                         ^

ERROR: space required after that ',' (ctx:VxV)
#198: FILE: security/keys/trusted-keys/trusted_tpm2.c:29:
+static u32 tpm2key_oid[] = { 2,23,133,10,1,5 };

I fixed them by hand. I will apply these now to my master branch first,
but can you just sanity check that your changes still work for you?

Cutting hairs, but better to be safe than sorry when doing even a single
change to the source code.

/Jarkko

  reply	other threads:[~2021-01-30 16:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 19:06 [PATCH v15 0/5] TPM 2.0 trusted key rework James Bottomley
2021-01-27 19:06 ` [PATCH v15 1/5] lib: add ASN.1 encoder James Bottomley
2021-01-27 19:06 ` [PATCH v15 2/5] oid_registry: Add TCG defined OIDS for TPM keys James Bottomley
2021-01-27 19:06 ` [PATCH v15 3/5] security: keys: trusted: fix TPM2 authorizations James Bottomley
2021-01-27 19:06 ` [PATCH v15 4/5] security: keys: trusted: use ASN.1 TPM2 key format for the blobs James Bottomley
2021-01-30 16:29   ` Jarkko Sakkinen [this message]
2021-01-30 17:12     ` James Bottomley
2021-01-27 19:06 ` [PATCH v15 5/5] security: keys: trusted: Make sealed key properly interoperable James Bottomley
2021-01-28  6:00 ` [PATCH v15 0/5] TPM 2.0 trusted key rework Jarkko Sakkinen
2021-02-10 15:58 ` [PATCH v15 3/5] security: keys: trusted: fix TPM2 authorizations David Howells
2021-02-10 16:12   ` James Bottomley
2021-02-12 11:55     ` Jarkko Sakkinen
2021-02-19 18:24 ` [PATCH v15 0/5] TPM 2.0 trusted key rework Jarkko Sakkinen
2021-02-19 18:35   ` James Bottomley
2021-02-20  2:39     ` Jarkko Sakkinen

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=YBWJVcM8/2tIlWHk@kernel.org \
    --to=jarkko@kernel.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=dhowells@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=zohar@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).