From: Jarkko Sakkinen <jarkko@kernel.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org,
Elaine Palmer <erpalmer@us.ibm.com>,
George Wilson <gcwilson@us.ibm.com>,
zgu@us.ibm.com
Subject: Re: [PATCH] doc: trusted-encrypted: updates with TEE as a new trust source (update)
Date: Sun, 10 Jan 2021 05:16:52 +0200 [thread overview]
Message-ID: <X/pxpAfn4MFsXT4g@kernel.org> (raw)
In-Reply-To: <CAFA6WYMt5+zX09bdgugSq9SgqF=V_OfOZee8fBEAv1thFLs3nA@mail.gmail.com>
On Mon, Jan 04, 2021 at 06:06:33PM +0530, Sumit Garg wrote:
> Hi Jarkko,
>
> On Fri, 11 Dec 2020 at 13:44, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> >
> > On Wed, Dec 09, 2020 at 11:42:49AM -0500, Mimi Zohar wrote:
> > > From: Elaine Palmer <erpalmer@us.ibm.com>
> > >
> > > Update trusted key documentation with additional comparisons between
> > > discrete TPMs and TEE.
> > >
> > > Signed-off-by: Elaine Palmer <erpalmer@us.ibm.com>
> >
> > Right, so OP-TEE is not the same as TEE. I did not know this and the
> > patch set does not underline this.
> >
> > I re-checked the patches and none of them say explicitly that OP-TEE
> > is an application living inside TEE.
>
> This patch-set provides a trust source based on generic TEE interface
> where underlying TEE implementations like OP-TEE (drivers/tee/optee/),
> AMD TEE (drivers/tee/amdtee/) etc. can easily be hooked up. And this
> is similar to the TPM interface where underlying TPM implementations
> like discrete TPM, virtual TPM, firmware TPM etc. can be easily hooked
> up.
>
> >
> > This essentially means that the backend needs to be renamed as "op_tee".
> >
>
> I don't see any need for this, see above.
Right, TEE is a protocol standard, just like TPM, and OP-TEE is one
implementation of this interface? I.e. OP-TEE does not define API
that is hard bound to OP-TEE?
Better to ask the very basic questions out and loud to get this
right.
/Jarkko
next prev parent reply other threads:[~2021-01-10 3:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 16:42 [PATCH] doc: trusted-encrypted: updates with TEE as a new trust source (update) Mimi Zohar
2020-12-11 8:14 ` Jarkko Sakkinen
2020-12-11 15:16 ` Mimi Zohar
2021-01-04 12:36 ` Sumit Garg
2021-01-10 3:16 ` Jarkko Sakkinen [this message]
2021-01-12 5:25 ` Sumit Garg
2021-01-13 21:23 ` Jarkko Sakkinen
2021-01-15 23:15 ` Elaine Palmer
2021-01-18 6:53 ` Sumit Garg
2021-01-20 14:21 ` Jarkko Sakkinen
2021-01-20 14:25 ` Jarkko Sakkinen
2021-01-04 12:15 ` Sumit Garg
2021-01-10 3:14 ` 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=X/pxpAfn4MFsXT4g@kernel.org \
--to=jarkko@kernel.org \
--cc=erpalmer@us.ibm.com \
--cc=gcwilson@us.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=sumit.garg@linaro.org \
--cc=zgu@us.ibm.com \
--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
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).