From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: [PATCH v2 0/3] tpm: retrieve digest size of unknown algorithms from TPM
Date: Mon, 10 Sep 2018 21:42:44 +0300 [thread overview]
Message-ID: <20180910184244.GC20225@linux.intel.com> (raw)
In-Reply-To: <20180905114202.7757-1-roberto.sassu@huawei.com>
On Wed, Sep 05, 2018 at 01:41:59PM +0200, Roberto Sassu wrote:
> The TPM driver currently relies on the crypto subsystem to determine the
> digest size of supported TPM algorithms. In the future, TPM vendors might
> implement new algorithms in their chips, and those algorithms might not
> be supported by the crypto subsystem.
>
> Usually, vendors provide patches for the new hardware, and likely
> the crypto subsystem will be updated before the new algorithm is
> introduced. However, old kernels might be updated later, after patches
> are included in the mainline kernel. This would leave the opportunity
> for attackers to misuse PCRs, as PCR banks with an unknown algorithm
> are not extended.
>
> This patch set provides a long term solution for this issue. If a TPM
> algorithm is not known by the crypto subsystem, the TPM driver retrieves
> the digest size from the TPM with a PCR read. All the PCR banks are
> extended, even if the algorithm is not yet supported by the crypto
> subsystem.
I'm sorry. I missed this before checking through the mails. In future,
please add me either to to-field so that they arrive to my inbox and
do not get filtered to linux-integrity folder, which I go through with
time at most once a week.
/Jarkko
next prev parent reply other threads:[~2018-09-10 23:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180905114202.7757-1-roberto.sassu@huawei.com>
[not found] ` <20180905114202.7757-3-roberto.sassu@huawei.com>
2018-09-05 13:43 ` EXTERNAL: [PATCH v2 2/3] tpm: modify tpm_pcr_read() definition to pass TPM hash algorithms Jeremy Boone
[not found] ` <e1d77563-81fd-36f0-648f-3325969b05af@huawei.com>
2018-09-16 12:30 ` Jarkko Sakkinen
2018-09-16 12:37 ` Winkler, Tomas
2018-09-16 19:21 ` Jarkko Sakkinen
2018-09-26 14:09 ` Mimi Zohar
2018-09-26 14:39 ` Roberto Sassu
2018-09-10 18:42 ` Jarkko Sakkinen [this message]
[not found] ` <20180905114202.7757-2-roberto.sassu@huawei.com>
2018-09-16 12:13 ` [PATCH v2 1/3] tpm: rename and export tpm2_digest and tpm2_algorithms Jarkko Sakkinen
[not found] ` <20180905114202.7757-4-roberto.sassu@huawei.com>
2018-09-16 12:37 ` [PATCH v2 3/3] tpm: retrieve digest size of unknown algorithms with PCR read Jarkko Sakkinen
2018-09-17 10:02 ` Roberto Sassu
2018-09-17 21:16 ` Jarkko Sakkinen
2018-09-18 7:14 ` Roberto Sassu
2018-09-18 18:54 ` 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=20180910184244.GC20225@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=roberto.sassu@huawei.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).