All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nayna <nayna@linux.vnet.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc: tpmdd-devel@lists.sourceforge.net, peterhuewe@gmx.de,
	tpmdd@selhorst.net, jgunthorpe@obsidianresearch.com,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/2] enhance TPM 2.0 extend function to support multiple PCR banks
Date: Thu, 26 Jan 2017 20:04:24 +0530	[thread overview]
Message-ID: <588A08F0.4070501@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170125233335.g5dmj43bgrulwmva@intel.com>



On 01/26/2017 05:03 AM, Jarkko Sakkinen wrote:
> On Wed, Jan 25, 2017 at 10:45:35PM +0200, Jarkko Sakkinen wrote:
>> On Fri, Jan 20, 2017 at 12:05:11PM -0500, Nayna Jain wrote:
>>> IMA extends its hash measurements in the TPM PCRs, based on policy.
>>> The existing in-kernel TPM extend function extends only the SHA1
>>> PCR bank. TPM 2.0 defines multiple PCR banks, to support different
>>> hash algorithms. The TCG TPM 2.0 Specification[1] recommends
>>> extending all active PCR banks to prevent malicious users from
>>> setting unused PCR banks with fake measurements and quoting them.
>>> This patch set adds support for extending all active PCR banks,
>>> as recommended.
>>>
>>> The first patch implements the TPM 2.0 capability to retrieve
>>> the list of active PCR banks.
>>>
>>> The second patch modifies the tpm_pcr_extend() and tpm2_pcr_extend()
>>> interface to support extending multiple PCR banks. The existing
>>> tpm_pcr_extend() interface expects only a SHA1 digest. Hence, to
>>> extend all active PCR banks with differing digest sizes for TPM 2.0,
>>> the SHA1 digest is padded with 0's as needed.
>>>
>>> [1] TPM 2.0 Specification referred here is "TCG PC Client Specific
>>> Platform Firmware Profile for TPM 2.0"
>>
>> I pushed these patches. I had to resolve merge conflicts caused
>> by the min_rsp_body_length parameter in tpm_transmit_cmd. Can you
>> verify that I didn't break anything?
>
> You have a bug in tpm2_get_pcr_allocation:
>
> rc = tpm_transmit_cmd(chip, buf.data, PAGE_SIZE, 9, 0,
> 		      "get tpm pcr allocation");
> if (rc < 0)
> 	goto out;
>
> You do not handle TPM error. Can you send a fix for this ASAP?

Oh!! Sure..
I see below fix should handle it.
if (rc)
   goto out:

Sending the patch...

Thanks & Regards,
    - Nayna

>
> /Jarkko
>

  reply	other threads:[~2017-01-26 14:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-20 17:05 [PATCH v6 0/2] enhance TPM 2.0 extend function to support multiple PCR banks Nayna Jain
2017-01-20 17:05 ` Nayna Jain
2017-01-20 17:05 ` [PATCH v6 1/2] tpm: implement TPM 2.0 capability to get active " Nayna Jain
2017-01-20 17:05   ` Nayna Jain
2017-01-26 12:23   ` [tpmdd-devel] " Stefan Berger
2017-01-27  6:30     ` Jarkko Sakkinen
2017-01-20 17:05 ` [PATCH v6 2/2] tpm: enhance TPM 2.0 PCR extend to support multiple banks Nayna Jain
2017-01-20 17:05   ` Nayna Jain
2017-01-23 15:19   ` Jarkko Sakkinen
2017-01-23 15:19     ` Jarkko Sakkinen
2017-01-23 16:41     ` Nayna
2017-01-24 11:59       ` Jarkko Sakkinen
2017-01-24 13:04         ` Nayna
2017-01-24 13:04           ` Nayna
2017-01-25 19:49           ` Jarkko Sakkinen
2017-01-25 19:49             ` Jarkko Sakkinen
2017-01-20 20:51 ` [PATCH v6 0/2] enhance TPM 2.0 extend function to support multiple PCR banks Jarkko Sakkinen
2017-01-20 20:51   ` Jarkko Sakkinen
2017-01-25 20:45 ` Jarkko Sakkinen
2017-01-25 20:45   ` Jarkko Sakkinen
2017-01-25 21:08   ` [tpmdd-devel] " Stefan Berger
2017-01-25 22:04     ` Jarkko Sakkinen
2017-01-25 22:52       ` Jarkko Sakkinen
2017-01-25 22:57         ` Jarkko Sakkinen
2017-01-25 23:33   ` Jarkko Sakkinen
2017-01-26 14:34     ` Nayna [this message]
2017-01-27 17:23   ` Nayna
2017-01-27 17:23     ` Nayna
2017-01-29 15:19     ` Jarkko Sakkinen
2017-01-29 15:19       ` Jarkko Sakkinen
2017-01-27 17:24   ` Nayna
2017-01-27 17:24     ` Nayna

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=588A08F0.4070501@linux.vnet.ibm.com \
    --to=nayna@linux.vnet.ibm.com \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    --cc=tpmdd-devel@lists.sourceforge.net \
    --cc=tpmdd@selhorst.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.