Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Mimi Zohar <zohar@linux.ibm.com>, dhowells@redhat.com
Cc: linux-integrity@vger.kernel.org, jejb@linux.ibm.com,
	sumit.garg@linaro.org
Subject: Re: KEYS-TRUSTED git
Date: Tue, 10 Sep 2019 15:21:25 +0100
Message-ID: <20190910142114.GA8682@linux.intel.com> (raw)
In-Reply-To: <20190909165200.npxq3hkft4bddv6v@linux.intel.com>

On Mon, Sep 09, 2019 at 05:52:00PM +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.

I use my tpmdd tree for trusted-keys changes too. For me managing two
trees is only adds to work and probably does not add that much value to
anyone else. The only glitch is the tree's name...

/Jarkko

      parent reply index

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08  0:10 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
2019-09-10 14:21     ` Jarkko Sakkinen [this message]

Reply instructions:

You may reply publically 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=20190910142114.GA8682@linux.intel.com \
    --to=jarkko.sakkinen@linux.intel.com \
    --cc=dhowells@redhat.com \
    --cc=jejb@linux.ibm.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=sumit.garg@linaro.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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org linux-integrity@archiver.kernel.org
	public-inbox-index linux-integrity

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/ public-inbox