From: Mimi Zohar <zohar-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: "Likun (Hw)" <hw.likun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: "linux-ima-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<linux-ima-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
"(tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org)"
<tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [Linux-ima-devel] [Question]: Question on the hash algorithm of evm and pcr_extend?
Date: Thu, 23 Feb 2017 10:54:30 -0500 [thread overview]
Message-ID: <1487865270.3193.124.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <806EF96D8ABD354A89C18BBED3F86165B8B0D2CC-DDyGIOodwTO05WiQPbXitQK1hpo4iccwjNknBlVQO8k@public.gmane.org>
On Thu, 2017-02-23 at 09:36 +0000, Likun (Hw) wrote:
> Hi,
>
> * Is there any plan to support other evm_hmac algorithms (like
> we done on ima file data hash algorithm), the sha2 or other recent
> algorithms are more hardened than sha1 after all.
The EVM hmac values are system local, so adding support for other hash
algorithms shouldn't be a problem. Similarly adding signature support
larger hash algorithms should be fine.
Patches are welcome to add this support.
> * We have supported arbitrary hash algorithms for ima file
> data measurement since commit
> e7a2ad7eb6f48ad80c70a22dd8167fb34b409466, but the ima template hash
> algorithm is still sha1 due to the tpm1.2 pcr limitation.
> But as we all know ,the tpm2 has supported sha2/sm3 and other
> algorithms , is there any approach to use TPM2.0 better ? For
> example , could we use sha2 as default digest algorithm, and when we
> meet tpm1.2, we truncate the digest from 32 to 20 bytes ?
The two patches that Nayna Jain just upstreamed determine the active PCR
banks and extend those banks with zero padded SHA1 hash into the
multiple TPM banks.
a06c59d417fb tpm: enhance TPM 2.0 PCR extend to support multiple banks
104e5f664d3a tpm: implement TPM 2.0 capability to get active PCR banks
These patches were a stop gap measure until support is added for a "hash
agile" IMA measurement format. It would be straight forward to replace
the TPM hash algorithm size used in the IMA measurement list with
something that is configurable(eg. Kconfig option), but that puts the
burden on the attestation servers to determine the hash size being used.
A better solution would be to add support for including multiple hashes
in the IMA measurement list. Whether we will ever support multiple
hashes in the measurement list is irrelevant, but it provides the needed
flexibility.
Mimi
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
prev parent reply other threads:[~2017-02-23 15:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 9:36 [Question]: Question on the hash algorithm of evm and pcr_extend? Likun (Hw)
[not found] ` <806EF96D8ABD354A89C18BBED3F86165B8B0D2CC-DDyGIOodwTO05WiQPbXitQK1hpo4iccwjNknBlVQO8k@public.gmane.org>
2017-02-23 15:54 ` Mimi Zohar [this message]
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=1487865270.3193.124.camel@linux.vnet.ibm.com \
--to=zohar-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=hw.likun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=linux-ima-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).