From: James Bottomley <jejb@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, zohar@linux.vnet.ibm.com,
jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
keyrings@vger.kernel.org
Subject: Re: [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module shutdown
Date: Tue, 03 Jul 2018 19:06:23 +0000 [thread overview]
Message-ID: <1530644783.3142.37.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1807040450340.32123@namei.org>
On Wed, 2018-07-04 at 04:51 +1000, James Morris wrote:
> On Tue, 3 Jul 2018, Jarkko Sakkinen wrote:
>
> > On Tue, Jul 03, 2018 at 08:26:55AM -0700, James Bottomley wrote:
> >
> > OK, I was not sure how that discussion went. I could add myself as
> > co-maintainer to MAINTAINERS because I anyway need to go through
> > all of these.
> >
> > If anyone does not vote against, I'll send a patch.
> >
>
> For Keys? That would would be useful to help reduce the workload on
> David.
Well, no, this was for trusted keys, which is the part of the key
infrastructure that goes via the TPM: The KEYS-TRUSTED part in the
MAINTAINERs file. There's still KEYS-ENCRYPTED, KEYS/KEYRING and
ASYMETRIC KEYS, which don't use the TPM.
However, I've no objection to consolidating the lot under a larger set
of maintainers ... I recently agreed to look at the asymmetric key TPM
patch because it's my area, but it also strays over into crypto,
keyring and asymmetric keys.
James
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <jejb@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, zohar@linux.vnet.ibm.com,
jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
keyrings@vger.kernel.org
Subject: Re: [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module shutdown
Date: Tue, 03 Jul 2018 12:06:23 -0700 [thread overview]
Message-ID: <1530644783.3142.37.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1807040450340.32123@namei.org>
On Wed, 2018-07-04 at 04:51 +1000, James Morris wrote:
> On Tue, 3 Jul 2018, Jarkko Sakkinen wrote:
>
> > On Tue, Jul 03, 2018 at 08:26:55AM -0700, James Bottomley wrote:
> >
> > OK, I was not sure how that discussion went. I could add myself as
> > co-maintainer to MAINTAINERS because I anyway need to go through
> > all of these.
> >
> > If anyone does not vote against, I'll send a patch.
> >
>
> For Keys? That would would be useful to help reduce the workload on
> David.
Well, no, this was for trusted keys, which is the part of the key
infrastructure that goes via the TPM: The KEYS-TRUSTED part in the
MAINTAINERs file. There's still KEYS-ENCRYPTED, KEYS/KEYRING and
ASYMETRIC KEYS, which don't use the TPM.
However, I've no objection to consolidating the lot under a larger set
of maintainers ... I recently agreed to look at the asymmetric key TPM
patch because it's my area, but it also strays over into crypto,
keyring and asymmetric keys.
James
WARNING: multiple messages have this Message-ID (diff)
From: jejb@linux.vnet.ibm.com (James Bottomley)
To: linux-security-module@vger.kernel.org
Subject: [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module shutdown
Date: Tue, 03 Jul 2018 12:06:23 -0700 [thread overview]
Message-ID: <1530644783.3142.37.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1807040450340.32123@namei.org>
On Wed, 2018-07-04 at 04:51 +1000, James Morris wrote:
> On Tue, 3 Jul 2018, Jarkko Sakkinen wrote:
>
> > On Tue, Jul 03, 2018 at 08:26:55AM -0700, James Bottomley wrote:
> >
> > OK, I was not sure how that discussion went. I could add myself as
> > co-maintainer to MAINTAINERS because I anyway need to go through
> > all of these.
> >
> > If anyone does not vote against, I'll send a patch.
> >
>
> For Keys???That would would be useful to help reduce the workload on?
> David.
Well, no, this was for trusted keys, which is the part of the key
infrastructure that goes via the TPM: The KEYS-TRUSTED part in the
MAINTAINERs file. There's still KEYS-ENCRYPTED, KEYS/KEYRING and
ASYMETRIC KEYS, which don't use the TPM.
However, I've no objection to consolidating the lot under a larger set
of maintainers ... I recently agreed to look at the asymmetric key TPM
patch because it's my area, but it also strays over into crypto,
keyring and asymmetric keys.
James
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: James Bottomley <jejb@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, zohar@linux.vnet.ibm.com,
jgg@ziepe.ca, linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, dhowells@redhat.com,
keyrings@vger.kernel.org
Subject: Re: [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module shutdown
Date: Tue, 03 Jul 2018 12:06:23 -0700 [thread overview]
Message-ID: <1530644783.3142.37.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.21.1807040450340.32123@namei.org>
On Wed, 2018-07-04 at 04:51 +1000, James Morris wrote:
> On Tue, 3 Jul 2018, Jarkko Sakkinen wrote:
>
> > On Tue, Jul 03, 2018 at 08:26:55AM -0700, James Bottomley wrote:
> >
> > OK, I was not sure how that discussion went. I could add myself as
> > co-maintainer to MAINTAINERS because I anyway need to go through
> > all of these.
> >
> > If anyone does not vote against, I'll send a patch.
> >
>
> For Keys? That would would be useful to help reduce the workload on
> David.
Well, no, this was for trusted keys, which is the part of the key
infrastructure that goes via the TPM: The KEYS-TRUSTED part in the
MAINTAINERs file. There's still KEYS-ENCRYPTED, KEYS/KEYRING and
ASYMETRIC KEYS, which don't use the TPM.
However, I've no objection to consolidating the lot under a larger set
of maintainers ... I recently agreed to look at the asymmetric key TPM
patch because it's my area, but it also strays over into crypto,
keyring and asymmetric keys.
James
next prev parent reply other threads:[~2018-07-03 19:06 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 19:30 [PATCH 0/2] Convert trusted keys to find and use the default TPM chip Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-06-26 19:30 ` [PATCH 1/2] tpm: Implement public tpm_put_chip() to release reference to chip Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-07-03 15:21 ` Jarkko Sakkinen
2018-07-03 15:21 ` Jarkko Sakkinen
2018-07-03 15:21 ` Jarkko Sakkinen
2018-06-26 19:30 ` [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module shutdown Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-06-26 19:30 ` Stefan Berger
2018-07-03 15:24 ` Jarkko Sakkinen
2018-07-03 15:24 ` Jarkko Sakkinen
2018-07-03 15:24 ` Jarkko Sakkinen
2018-07-03 15:26 ` James Bottomley
2018-07-03 15:26 ` James Bottomley
2018-07-03 15:26 ` James Bottomley
2018-07-03 16:51 ` Jarkko Sakkinen
2018-07-03 16:51 ` Jarkko Sakkinen
2018-07-03 16:51 ` Jarkko Sakkinen
2018-07-03 18:51 ` James Morris
2018-07-03 18:51 ` James Morris
2018-07-03 18:51 ` James Morris
2018-07-03 19:06 ` James Bottomley [this message]
2018-07-03 19:06 ` James Bottomley
2018-07-03 19:06 ` James Bottomley
2018-07-03 19:06 ` James Bottomley
2018-07-04 13:52 ` Jarkko Sakkinen
2018-07-04 13:52 ` Jarkko Sakkinen
2018-07-04 13:52 ` Jarkko Sakkinen
2018-07-04 13:52 ` 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=1530644783.3142.37.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=jmorris@namei.org \
--cc=keyrings@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=zohar@linux.vnet.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.