[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180704135235.GA6724@linux.intel.com>
Date: Wed, 4 Jul 2018 16:52:35 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: James Bottomley <jejb@...ux.vnet.ibm.com>
Cc: James Morris <jmorris@...ei.org>,
Stefan Berger <stefanb@...ux.vnet.ibm.com>,
linux-integrity@...r.kernel.org, zohar@...ux.vnet.ibm.com,
jgg@...pe.ca, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org, dhowells@...hat.com,
keyrings@...r.kernel.org
Subject: Re: [PATCH 2/2] KEYS: trusted: Find tpm_chip and use it until module
shutdown
On Tue, Jul 03, 2018 at 12:06:23PM -0700, James Bottomley wrote:
> 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.
Should 2/2 be rolled through my tree? 1/2 is a tpm patch.
/Jarkko
Powered by blists - more mailing lists