All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: James Bottomley <jejb@linux.ibm.com>,
	Jerry Snitselaar <jsnitsel@redhat.com>,
	Stefan Berger <stefanb@linux.ibm.com>,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Extend trusted keys documentation for TPM 2.0
Date: Sun, 02 Dec 2018 23:04:26 +0000	[thread overview]
Message-ID: <20181202230426.GA6718@linux.intel.com> (raw)
In-Reply-To: <1543763436.4216.196.camel@linux.ibm.com>

On Sun, Dec 02, 2018 at 10:10:36AM -0500, Mimi Zohar wrote:
> Are you asking about coordinating staging the trusted key patches to
> be upstreamed or about moving portions of the encrypted keys code out
> of the keyring subsystem?
> 
> I'm not sure there needs to be a separate encrypted-keys pull request.
>  Either they can be upstreamed via the TPM or the integrity subsystem
> for now.

Nothing that ought to be rushed.

I'm speaking about this situation:

1. TPM 1.x trusted keys code is inside keyring subsystem.
2. TPM 2.0 trusted keys code is inside tpm subsystem.

We are doing effort to make TPM subsystem more friendly to send custom
commands outside (tpm_buf, my unnesting effort in progress, Tomas' clean
ups for TPM 1.x code) so I'm more dilated to the 2nd option.

/Jarkko

WARNING: multiple messages have this Message-ID (diff)
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: James Bottomley <jejb@linux.ibm.com>,
	Jerry Snitselaar <jsnitsel@redhat.com>,
	Stefan Berger <stefanb@linux.ibm.com>,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: Extend trusted keys documentation for TPM 2.0
Date: Sun, 2 Dec 2018 15:04:26 -0800	[thread overview]
Message-ID: <20181202230426.GA6718@linux.intel.com> (raw)
In-Reply-To: <1543763436.4216.196.camel@linux.ibm.com>

On Sun, Dec 02, 2018 at 10:10:36AM -0500, Mimi Zohar wrote:
> Are you asking about coordinating staging the trusted key patches to
> be upstreamed or about moving portions of the encrypted keys code out
> of the keyring subsystem?
> 
> I'm not sure there needs to be a separate encrypted-keys pull request.
>  Either they can be upstreamed via the TPM or the integrity subsystem
> for now.

Nothing that ought to be rushed.

I'm speaking about this situation:

1. TPM 1.x trusted keys code is inside keyring subsystem.
2. TPM 2.0 trusted keys code is inside tpm subsystem.

We are doing effort to make TPM subsystem more friendly to send custom
commands outside (tpm_buf, my unnesting effort in progress, Tomas' clean
ups for TPM 1.x code) so I'm more dilated to the 2nd option.

/Jarkko

  reply	other threads:[~2018-12-02 23:04 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-19 10:17 [PATCH] docs: Extend trusted keys documentation for TPM 2.0 Stefan Berger
2018-10-19 10:17 ` Stefan Berger
2018-10-19 23:07 ` Randy Dunlap
2018-10-19 23:07   ` Randy Dunlap
2018-11-05 16:57 ` Dan Williams
2018-11-05 16:57   ` Dan Williams
2018-11-05 20:42 ` Jerry Snitselaar
2018-11-05 20:42   ` Jerry Snitselaar
2018-11-06 16:00   ` Jerry Snitselaar
2018-11-06 16:00     ` Jerry Snitselaar
2018-11-06 16:14     ` Joshua Lock
2018-11-07  0:53       ` Roberts, William C
2018-11-07  0:53         ` Roberts, William C
2018-11-06 16:46 ` Jerry Snitselaar
2018-11-06 16:46   ` Jerry Snitselaar
2018-11-06 18:17   ` Mimi Zohar
2018-11-06 18:17     ` Mimi Zohar
2018-11-30 23:45     ` Jarkko Sakkinen
2018-11-30 23:45       ` Jarkko Sakkinen
2018-11-30 23:46       ` Jarkko Sakkinen
2018-11-30 23:46         ` Jarkko Sakkinen
2018-12-02 15:10         ` Mimi Zohar
2018-12-02 15:10           ` Mimi Zohar
2018-12-02 23:04           ` Jarkko Sakkinen [this message]
2018-12-02 23:04             ` 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=20181202230426.GA6718@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=jejb@linux.ibm.com \
    --cc=jsnitsel@redhat.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stefanb@linux.ibm.com \
    --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 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.