From: Jarkko Sakkinen <jarkko.sakkinen@linux•intel.com>
To: Sumit Garg <sumit.garg@linaro•org>
Cc: "tee-dev @ lists . linaro . org" <tee-dev@lists•linaro.org>,
Daniel Thompson <daniel.thompson@linaro•org>,
op-tee@lists•trustedfirmware.org,
Jonathan Corbet <corbet@lwn•net>,
James Bottomley <jejb@linux•ibm.com>,
Janne Karhunen <janne.karhunen@gmail•com>,
Linux Doc Mailing List <linux-doc@vger•kernel.org>,
James Morris <jmorris@namei•org>,
Mimi Zohar <zohar@linux•ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
dhowells@redhat•com, linux-security-module@vger•kernel.org,
"open list:ASYMMETRIC KEYS" <keyrings@vger•kernel.org>,
Markus Wamser <Markus.Wamser@mixed-mode•de>,
Casey Schaufler <casey@schaufler-ca•com>,
linux-integrity@vger•kernel.org,
Jens Wiklander <jens.wiklander@linaro•org>,
linux-arm-kernel <linux-arm-kernel@lists•infradead.org>,
"Serge E. Hallyn" <serge@hallyn•com>
Subject: Re: [PATCH v4 1/4] KEYS: trusted: Add generic trusted keys framework
Date: Tue, 2 Jun 2020 10:14:07 +0300 [thread overview]
Message-ID: <20200602071407.GB16602@linux.intel.com> (raw)
In-Reply-To: <CAFA6WYP55W2xKtjHWWwu6Pbqy2TGY=eymwAoXxQh-5mF8deR6A@mail.gmail.com>
On Mon, Jun 01, 2020 at 02:41:55PM +0530, Sumit Garg wrote:
> > This, I think is wrong. You should have a compile time flag for TPM e.g.
> > CONFIG_TRUSTED_TPM, not this dynamic mess.
> >
>
> The whole idea to have it dynamic was to have a common trusted keys
> module which could support both TPM and TEE implementation depending
> on hardware. I guess it may be useful in scenarios where a particular
> hardware supports a TPM chip while other doesn't but both need to run
> a common kernel image.
For now it should only scale to what is needed. No problems refining
it later when there is something to enable.
/Jarkko
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-02 7:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 9:40 [PATCH v4 0/4] Introduce TEE based Trusted Keys support Sumit Garg
2020-05-06 9:40 ` [PATCH v4 1/4] KEYS: trusted: Add generic trusted keys framework Sumit Garg
2020-05-14 0:25 ` Jarkko Sakkinen
2020-05-14 11:23 ` Sumit Garg
2020-05-15 0:00 ` Jarkko Sakkinen
2020-06-01 2:00 ` Jarkko Sakkinen
2020-06-01 8:50 ` Sumit Garg
2020-06-02 7:08 ` Jarkko Sakkinen
2020-06-01 2:11 ` Jarkko Sakkinen
2020-06-01 9:11 ` Sumit Garg
2020-06-02 7:14 ` Jarkko Sakkinen [this message]
2020-06-02 8:40 ` Sumit Garg
2020-05-06 9:40 ` [PATCH v4 2/4] KEYS: trusted: Introduce TEE based Trusted Keys Sumit Garg
2020-05-14 0:28 ` Jarkko Sakkinen
2020-05-14 7:27 ` Sumit Garg
2020-05-14 23:43 ` Jarkko Sakkinen
2020-05-06 9:40 ` [PATCH v4 3/4] doc: trusted-encrypted: updates with TEE as a new trust source Sumit Garg
2020-05-14 0:29 ` Jarkko Sakkinen
2020-05-06 9:40 ` [PATCH v4 4/4] MAINTAINERS: Add entry for TEE based Trusted Keys Sumit Garg
2020-05-14 0:35 ` Jarkko Sakkinen
2020-05-12 9:20 ` [PATCH v4 0/4] Introduce TEE based Trusted Keys support Sumit Garg
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=20200602071407.GB16602@linux.intel.com \
--to=jarkko.sakkinen@linux$(echo .)intel.com \
--cc=Markus.Wamser@mixed-mode$(echo .)de \
--cc=casey@schaufler-ca$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=daniel.thompson@linaro$(echo .)org \
--cc=dhowells@redhat$(echo .)com \
--cc=janne.karhunen@gmail$(echo .)com \
--cc=jejb@linux$(echo .)ibm.com \
--cc=jens.wiklander@linaro$(echo .)org \
--cc=jmorris@namei$(echo .)org \
--cc=keyrings@vger$(echo .)kernel.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-integrity@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-security-module@vger$(echo .)kernel.org \
--cc=op-tee@lists$(echo .)trustedfirmware.org \
--cc=serge@hallyn$(echo .)com \
--cc=sumit.garg@linaro$(echo .)org \
--cc=tee-dev@lists$(echo .)linaro.org \
--cc=zohar@linux$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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