Linux-Integrity Archive on lore.kernel.org
 help / color / Atom feed
From: Mimi Zohar <zohar@linux.ibm.com>
To: Roberto Sassu <roberto.sassu@huawei.com>,
	"linux-integrity@vger.kernel.org"
	<linux-integrity@vger.kernel.org>
Cc: Jerry Snitselaar <jsnitsel@redhat.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Silviu Vlasceanu <Silviu.Vlasceanu@huawei.com>
Subject: Re: [PATCH v3 2/2] ima: support calculating the boot_aggregate based on different TPM banks
Date: Tue, 04 Feb 2020 12:27:44 -0500
Message-ID: <1580837264.5585.78.camel@linux.ibm.com> (raw)
In-Reply-To: <01986ba728014571a3907fef9c69ff2c@huawei.com>

On Tue, 2020-02-04 at 13:37 +0000, Roberto Sassu wrote:
> > -----Original Message-----
> > From: linux-integrity-owner@vger.kernel.org [mailto:linux-integrity-
> > owner@vger.kernel.org] On Behalf Of Mimi Zohar
> > Sent: Thursday, January 30, 2020 5:23 PM
> > To: linux-integrity@vger.kernel.org
> > Cc: Jerry Snitselaar <jsnitsel@redhat.com>; James Bottomley
> > <James.Bottomley@HansenPartnership.com>; linux-
> > kernel@vger.kernel.org; Mimi Zohar <zohar@linux.ibm.com>
> > Subject: [PATCH v3 2/2] ima: support calculating the boot_aggregate based
> > on different TPM banks
> > 
> > Calculating the boot_aggregate attempts to read the TPM SHA1 bank,
> > assuming it is always enabled.  With TPM 2.0 hash agility, TPM chips
> > could support multiple TPM PCR banks, allowing firmware to configure and
> > enable different banks.
> > 
> > Instead of hard coding the TPM 2.0 bank hash algorithm used for calculating
> > the boot-aggregate, use the same hash algorithm for reading the TPM PCRs
> > as
> > for calculating the boot aggregate digest.  Preference is given to the
> > configured IMA default hash algorithm.
> > 
> > For TPM 1.2 SHA1 is the only supported hash algorithm.
> > 
> > Reported-by: Jerry Snitselaar <jsnitsel@redhat.com>
> > Suggested-by: Roberto Sassu <roberto.sassu@huawei.com>
> > Signed-off-by: Mimi Zohar <zohar@linux.ibm.com>
> > ---
> >  security/integrity/ima/ima_crypto.c | 45
> > ++++++++++++++++++++++++++++++++++++-
> >  1 file changed, 44 insertions(+), 1 deletion(-)
> > 
> > diff --git a/security/integrity/ima/ima_crypto.c
> > b/security/integrity/ima/ima_crypto.c
> > index 7967a6904851..a020aaefdea8 100644
> > --- a/security/integrity/ima/ima_crypto.c
> > +++ b/security/integrity/ima/ima_crypto.c
> > @@ -656,13 +656,34 @@ static void __init ima_pcrread(u32 idx, struct
> > tpm_digest *d)
> >  		pr_err("Error Communicating to TPM chip\n");
> >  }
> > 
> > +static enum hash_algo get_hash_algo(const char *algname)
> > +{
> > +	int i;
> > +
> > +	for (i = 0; i < HASH_ALGO__LAST; i++) {
> > +		if (strcmp(algname, hash_algo_name[i]) == 0)
> > +			break;
> > +	}
> > +
> > +	return i;
> > +}
> > +
> >  /*
> > - * Calculate the boot aggregate hash
> > + * The boot_aggregate is a cumulative hash over TPM registers 0 - 7.  With
> > + * TPM 1.2 the boot_aggregate was based on reading the SHA1 PCRs, but
> > with
> > + * TPM 2.0 hash agility, TPM chips could support multiple TPM PCR banks,
> > + * allowing firmware to configure and enable different banks.
> > + *
> > + * Knowing which TPM bank is read to calculate the boot_aggregate digest
> > + * needs to be conveyed to a verifier.  For this reason, use the same
> > + * hash algorithm for reading the TPM PCRs as for calculating the boot
> > + * aggregate digest as stored in the measurement list.
> >   */
> >  static int __init ima_calc_boot_aggregate_tfm(char *digest,
> >  					      struct crypto_shash *tfm)
> >  {
> >  	struct tpm_digest d = { .alg_id = TPM_ALG_SHA1, .digest = {0} };
> > +	enum hash_algo crypto_id;
> >  	int rc;
> >  	u32 i;
> >  	SHASH_DESC_ON_STACK(shash, tfm);
> > @@ -673,6 +694,28 @@ static int __init ima_calc_boot_aggregate_tfm(char
> > *digest,
> >  	if (rc != 0)
> >  		return rc;
> > 
> > +	crypto_id = get_hash_algo(crypto_shash_alg_name(tfm));
> > +	if (crypto_id == HASH_ALGO__LAST) {
> > +		pr_devel("unknown hash algorithm (%s), failing to read
> > PCRs.\n",
> > +			 crypto_shash_alg_name(tfm));
> > +		return 0;
> > +	}
> > +
> > +	for (i = 0; i < ima_tpm_chip->nr_allocated_banks; i++) {
> > +		if (ima_tpm_chip->allocated_banks[i].crypto_id ==
> > crypto_id) {
> > +			d.alg_id = ima_tpm_chip->allocated_banks[i].alg_id;
> > +			break;
> > +		}
> > +	}
> > +	if (i == ima_tpm_chip->nr_allocated_banks) {
> > +		pr_devel("TPM %s bank not allocated, failing to read
> > PCRs.\n",
> > +			 crypto_shash_alg_name(tfm));
> > +		return 0;
> > +	}
> > +
> > +	pr_devel("calculating the boot-aggregregate based on TPM
> > bank: %04x\n",
> > +		  d.alg_id);
> > +
> >  	/* cumulative sha1 over tpm registers 0-7 */
> >  	for (i = TPM_PCR0; i < TPM_PCR8; i++) {
> >  		ima_pcrread(i, &d);
> 
> The third argument of crypto_shash_update() should be
> crypto_shash_digestsize(tfm).

Thanks!  At this point we know the hash algorithm, so we could use
hash_digest_size[].

Mimi


      reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 16:22 [PATCH v3 1/2] ima: support calculating the boot aggregate based on non-SHA1 algorithms Mimi Zohar
2020-01-30 16:22 ` [PATCH v3 2/2] ima: support calculating the boot_aggregate based on different TPM banks Mimi Zohar
2020-01-30 16:53   ` Lakshmi Ramasubramanian
2020-01-30 16:54   ` Roberto Sassu
2020-01-30 17:32     ` Mimi Zohar
2020-02-04 13:37   ` Roberto Sassu
2020-02-04 17:27     ` 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=1580837264.5585.78.camel@linux.ibm.com \
    --to=zohar@linux.ibm.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Silviu.Vlasceanu@huawei.com \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@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

Linux-Integrity Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-integrity/0 linux-integrity/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-integrity linux-integrity/ https://lore.kernel.org/linux-integrity \
		linux-integrity@vger.kernel.org
	public-inbox-index linux-integrity

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-integrity


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git