From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: zohar@linux.ibm.com, jejb@linux.ibm.com, corbet@lwn.net,
casey@schaufler-ca.com, janne.karhunen@gmail.com,
kgoldman@us.ibm.com, david.safford@ge.com, monty.wiseman@ge.com,
daniel.thompson@linaro.org, keyrings@vger.kernel.org,
linux-integrity@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, tee-dev@lists.linaro.org
Subject: Re: [PATCH] doc: trusted-encrypted: updates with TEE as a new trust source
Date: Tue, 31 Mar 2020 15:01:25 +0300 [thread overview]
Message-ID: <20200331120125.GE8295@linux.intel.com> (raw)
In-Reply-To: <1585636165-22481-1-git-send-email-sumit.garg@linaro.org>
On Tue, Mar 31, 2020 at 11:59:25AM +0530, Sumit Garg wrote:
> Update documentation for Trusted and Encrypted Keys with TEE as a new
> trust source. Following is brief description of updates:
>
> - Add a section to demostrate a list of supported devices along with
> their security properties/guarantees.
> - Add a key generation section.
> - Updates for usage section including differences specific to a trust
> source.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
Thanks for doing this. Looks like a lot of effort has gone to this.
Giving better feedback later.
/Jarkko
next prev parent reply other threads:[~2020-03-31 12:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-31 6:29 [PATCH] doc: trusted-encrypted: updates with TEE as a new trust source Sumit Garg
2020-03-31 12:01 ` Jarkko Sakkinen [this message]
2020-04-16 17:46 ` Jarkko Sakkinen
2020-04-17 4:57 ` Sumit Garg
2020-04-17 23:56 ` 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=20200331120125.GE8295@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=casey@schaufler-ca.com \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=david.safford@ge.com \
--cc=janne.karhunen@gmail.com \
--cc=jejb@linux.ibm.com \
--cc=keyrings@vger.kernel.org \
--cc=kgoldman@us.ibm.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=monty.wiseman@ge.com \
--cc=sumit.garg@linaro.org \
--cc=tee-dev@lists.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
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).