From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2, RESEND 2/3] tpm: modify tpm_pcr_read() definition to pass TPM hash algorithms
Date: Sat, 22 Sep 2018 00:57:01 +0300 [thread overview]
Message-ID: <20180921215701.GA23799@linux.intel.com> (raw)
In-Reply-To: <411432db-ea57-a537-05d3-0b53008bef27@huawei.com>
On Fri, Sep 21, 2018 at 12:24:15PM +0200, Roberto Sassu wrote:
> On 9/17/2018 11:38 AM, Roberto Sassu wrote:
> > Currently the TPM driver allows other kernel subsystems to read only the
> > SHA1 PCR bank. This patch modifies the parameters of tpm_pcr_read() and
> > tpm2_pcr_read() to pass an array of tpm_digest structures, which contains
> > the desired hash algorithms. Initially, the array size is limited to 1.
>
> Jarkko, is this patch ok?
>
> Mimi, I wait for your review of the IMA part.
>
> Roberto
Oops, just bumped into these. Have to check next week. Please add me to
either to- or cc-field in the future.
/Jarkko
next prev parent reply other threads:[~2018-09-22 3:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180917093820.20500-1-roberto.sassu@huawei.com>
[not found] ` <20180917093820.20500-3-roberto.sassu@huawei.com>
[not found] ` <411432db-ea57-a537-05d3-0b53008bef27@huawei.com>
2018-09-21 13:59 ` [PATCH v2, RESEND 2/3] tpm: modify tpm_pcr_read() definition to pass TPM hash algorithms Mimi Zohar
2018-09-21 21:57 ` Jarkko Sakkinen [this message]
2018-09-25 13:27 ` Jarkko Sakkinen
[not found] ` <20180917093820.20500-4-roberto.sassu@huawei.com>
2018-09-25 14:00 ` [PATCH v2, RESEND 3/3] tpm: retrieve digest size of unknown algorithms with PCR read Jarkko Sakkinen
2018-09-26 14:40 ` [PATCH v2, RESEND 0/3] tpm: retrieve digest size of unknown algorithms from TPM Mimi Zohar
2018-09-26 18:03 ` Mimi Zohar
2018-09-27 6:50 ` Roberto Sassu
2018-09-27 13:43 ` Mimi Zohar
2018-09-27 13:50 ` 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=20180921215701.GA23799@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=roberto.sassu@huawei.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).