From: Mimi Zohar <zohar@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: dhowells@redhat.com, linux-integrity@vger.kernel.org,
jejb@linux.ibm.com, sumit.garg@linaro.org
Subject: Re: KEYS-TRUSTED git
Date: Sun, 15 Sep 2019 16:53:16 -0400 [thread overview]
Message-ID: <1568580796.5055.2.camel@linux.ibm.com> (raw)
In-Reply-To: <20190913133228.GE7412@linux.intel.com>
On Fri, 2019-09-13 at 14:32 +0100, Jarkko Sakkinen wrote:
> On Mon, Sep 09, 2019 at 01:24:58PM -0400, Mimi Zohar wrote:
> > On Mon, 2019-09-09 at 17:52 +0100, Jarkko Sakkinen wrote:
> > > On Sun, Sep 08, 2019 at 10:20:31AM -0400, Mimi Zohar wrote:
> > > > Thanks, Jarkko. Agreed, trusted keys is becoming more than just TPM
> > > > based keys. Now would be a good time to set up at least a separate
> > > > branch or GIT repo.
> > >
> > > I created a tree for trusted keys:
> > >
> > > http://git.infradead.org/users/jjs/linux-trusted-keys.git
> > >
> > > The remaining issue before I send a patch to update MAINTAINERS is whether
> > > the flow goes through David to Linus or directly to Linus.
> >
> > David?
>
> I think using tpmdd tree makes sense because there is so much
> correlation.
Yes, agreed.
Mimi
next prev parent reply other threads:[~2019-09-15 20:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 0:10 KEYS-TRUSTED git Jarkko Sakkinen
2019-09-08 14:20 ` Mimi Zohar
2019-09-09 6:27 ` Sumit Garg
2019-09-09 10:40 ` Mimi Zohar
2019-09-09 16:36 ` Jarkko Sakkinen
2019-09-10 5:13 ` Sumit Garg
2019-09-13 13:34 ` Jarkko Sakkinen
2019-09-10 11:43 ` Jarkko Sakkinen
2019-09-10 12:32 ` Sumit Garg
2019-09-11 9:27 ` Jarkko Sakkinen
2019-09-11 9:29 ` Jarkko Sakkinen
2019-09-11 9:36 ` Jarkko Sakkinen
2019-09-11 9:58 ` Sumit Garg
2019-09-11 11:28 ` Sumit Garg
2019-09-09 16:33 ` Jarkko Sakkinen
2019-09-09 16:52 ` Jarkko Sakkinen
2019-09-09 17:24 ` Mimi Zohar
2019-09-13 13:32 ` Jarkko Sakkinen
2019-09-15 20:53 ` Mimi Zohar [this message]
2019-09-10 14:21 ` 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=1568580796.5055.2.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=sumit.garg@linaro.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 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).