All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lakshmi Ramasubramanian <nramas@linux.microsoft.com>
To: Roberto Sassu <roberto.sassu@huawei.com>,
	linux-integrity@vger.kernel.org, Mimi Zohar <zohar@linux.ibm.com>
Subject: Re: Does IMA support SHA-256 PCR banks?
Date: Wed, 11 Dec 2019 09:35:09 -0800	[thread overview]
Message-ID: <4673b391-6936-d2c1-bbd1-cd5daf6937f7@linux.microsoft.com> (raw)
In-Reply-To: <36fb73d7534f47b6906c348792bd5d96@huawei.com>

On 12/11/19 12:45 AM, Roberto Sassu wrote:

> 
> Hi Lakshmi
> 
> currently the SHA256 PCR bank is extended with a padded SHA1.
> 
> Some time ago, I posted some patches to support the TGC Crypto Agile format:
> 
> https://lkml.org/lkml/2017/5/16/369
> 
> However, this is a bit complicate because the current format does not follow
> the TCG standard. A work to support the new IMA Canonical Event Log format
> has been presented at LSS:
> 
> https://static.sched.com/hosted_files/lssna18/03/lss_2018_slides_V4.pdf
> 
> Given that the patches are very invasive, to me seems a good idea to split this
> work in two parts: first, extend PCRs with the correct digest and second
> change the measurement list format.
> 
> For the first part, the patch will be very simple, as IMA will just query the TPM
> to get the list of hash algorithms and will calculate all the digests in
> ima_calc_field_array_hash().
> 
> Also, the first part would be sufficient for remote attestation, as the data used
> to calculate the digests is passed to the verifier. The verifier can calculate by
> himself the digest of non-SHA1 PCR banks, even if they are not included in the
> measurement list.
> 
> Roberto
> 

Thanks Roberto for the info and the link to the related patches posted 
earlier. I'll take a look at the patches.

thanks,
  -lakshmi


  reply	other threads:[~2019-12-11 17:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10 22:37 Does IMA support SHA-256 PCR banks? Lakshmi Ramasubramanian
2019-12-11  8:45 ` Roberto Sassu
2019-12-11 17:35   ` Lakshmi Ramasubramanian [this message]
2019-12-25 16:46   ` Ken Goldman
2020-01-07  8:58     ` Roberto Sassu

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=4673b391-6936-d2c1-bbd1-cd5daf6937f7@linux.microsoft.com \
    --to=nramas@linux.microsoft.com \
    --cc=linux-integrity@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 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.