Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org, jejb@linux.ibm.com,
	dhowells@redhat.com
Subject: Re: KEYS-TRUSTED git
Date: Fri, 13 Sep 2019 14:34:46 +0100
Message-ID: <20190913133446.GF7412@linux.intel.com> (raw)
In-Reply-To: <CAFA6WYP6enHJBSsgzvTqzFEQwaW3ye2NrdnaxDMRCS1BC8mpsw@mail.gmail.com>

On Tue, Sep 10, 2019 at 10:43:27AM +0530, Sumit Garg wrote:
> On Mon, 9 Sep 2019 at 22:06, Jarkko Sakkinen
> <jarkko.sakkinen@linux.intel.com> wrote:
> >
> > On Mon, Sep 09, 2019 at 11:57:45AM +0530, Sumit Garg wrote:
> > > For Trusted Execution Environment (TEE) as a new "trust" method, I
> > > have tried to document it here [1]. Please share your thoughts on this
> > > patch [1] in case I missed something. I would be happy to incorporate
> > > your feedback. Also, can you elaborate on "comparison to the TPM",
> > > what specifics parameters are you looking for documentation?
> >
> > I think the right order is actually:
> >
> > 1. Set up the GIT tree.
> > 2. Merge your TEE patches (when they pass the review phase).
> > 3. Come up with the documentation.
> 
> Sounds good to me.

Come to 2nd thoughts. As long as the master has your changes, James
should be fine and James' changes also work as a test bed for your
changes. Decided to postpone.

/Jarkko

  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 [this message]
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

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=20190913133446.GF7412@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


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