From: Mimi Zohar <zohar@linux.ibm.com>
To: Sumit Garg <sumit.garg@linaro.org>,
Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: linux-integrity@vger.kernel.org, jejb@linux.ibm.com,
dhowells@redhat.com, Kenneth Goldman <kgoldman@us.ibm.com>,
David Safford <david.safford@ge.com>,
Monty Wiseman <monty.wiseman@ge.com>
Subject: Re: KEYS-TRUSTED git
Date: Mon, 09 Sep 2019 06:40:01 -0400 [thread overview]
Message-ID: <1568025601.4614.253.camel@linux.ibm.com> (raw)
In-Reply-To: <CAFA6WYPq8Tq6=jTqnWQf9w9pzdJu8AcX-CFBWPwoVmMaLEJKhg@mail.gmail.com>
[Cc'ing Ken, Dave, & Monty]
On Mon, 2019-09-09 at 11:57 +0530, Sumit Garg wrote:
> On Sun, 8 Sep 2019 at 19:50, Mimi Zohar <zohar@linux.ibm.com> wrote:
> > Are all "trust" methods equivalent? As new "trust" methods are
> > defined, there should be a document describing the trust method, with
> > a comparison to the TPM.
>
> 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?
For example, the security properties/guarantees of a hardware TPM are
different than a software TPM. Could we capture that difference in
chart form? As new "trust" methods are added, include that
information in the chart and extend the chart with other information,
as needed.
Mimi
>
> [1] https://patchwork.kernel.org/patch/11065679/
>
> -Sumit
next prev parent reply other threads:[~2019-09-09 10:40 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 [this message]
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
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=1568025601.4614.253.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=david.safford@ge.com \
--cc=dhowells@redhat.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jejb@linux.ibm.com \
--cc=kgoldman@us.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=monty.wiseman@ge.com \
--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).