From: Mimi Zohar <zohar@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
linux-integrity@vger.kernel.org
Subject: Re: TPM legacy
Date: Sun, 02 Dec 2018 10:23:46 -0500 [thread overview]
Message-ID: <1543764226.4216.205.camel@linux.ibm.com> (raw)
In-Reply-To: <20181130233501.GA32256@linux.intel.com>
On Fri, 2018-11-30 at 15:35 -0800, Jarkko Sakkinen wrote:
> Hi
>
> Some things that came up at LSS.
>
> First, would it be time to drop 1.1b bits? What advantages this would
> bring? AFAIK Peter is a strong supporter of this.
>
> In the hall way discussions, I talked with Tomas Winkler that it would
> make sense to add CONFIG_TCG_TPM1 flag to completely leave out all TPM
> 1.x bits from the kernel.
>
> TPM 1.x stuff is not exactly legacy but especially on IoT does not make
> sense to carry that code with.
New systems might be shipping with only TPM 2.0, but it still needs to
be supported for existing systems, probably for quite a while. Having
the option to build the kernel with TPM 1.2, TPM 2.0 or both, is
acceptable.
Mimi
next prev parent reply other threads:[~2018-12-02 15:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 23:35 TPM legacy Jarkko Sakkinen
2018-12-02 15:23 ` Mimi Zohar [this message]
2018-12-02 18:29 ` James Bottomley
2018-12-02 23:13 ` Jarkko Sakkinen
2018-12-03 15:01 ` Aw: " Peter Huewe
2018-12-03 17:29 ` Jason Gunthorpe
2018-12-03 17:55 ` Jarkko Sakkinen
2018-12-03 17:55 ` Jarkko Sakkinen
2018-12-03 18:00 ` Peter Huewe
2018-12-03 18:09 ` Jason Gunthorpe
2018-12-03 18:15 ` Jarkko Sakkinen
2018-12-03 18:15 ` Jarkko Sakkinen
2018-12-03 17:30 ` Jarkko Sakkinen
2018-12-02 23:08 ` 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=1543764226.4216.205.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.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).