All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>, Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org
Subject: Re: ima pcr question
Date: Fri, 17 Jan 2020 15:00:11 -0800	[thread overview]
Message-ID: <1579302011.13499.9.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200117222920.2d42m3ahxznl64em@cantor>

On Fri, 2020-01-17 at 15:29 -0700, Jerry Snitselaar wrote:
> On Mon Jan 13 20, Mimi Zohar wrote:
> > On Mon, 2020-01-13 at 17:06 -0700, Jerry Snitselaar wrote:
> > > We had a report of messages from ima saying "Error communicating
> > > with
> > > TPM".  Looking into it a bit, it looks like with some Dell
> > > systems
> > > (possibly others as well) in the bios they can set the hash
> > > algorithm
> > > being used. In this case with that set to sha256 the messages
> > > appear. Flipping the system to using sha1 makes them disappear.
> > > Looking at the ima code, ima_calc_boot_aggregate_tfm hard codes
> > > using
> > > sha1. Should that be changed to use whatever the default is in
> > > the
> > > config, or possibly find out from the tpm what algorithm is being
> > > used?
> > 
> > The ima-ng template contains two digests.  The first digest is the
> > value being extended into the TPM, while the second digest is
> > either
> > the boot aggregate or file data hash.  It sounds like the problem
> > is
> > with the first digest.  Changing the boot-aggregate to use sha256
> > might be a good idea, but probably won't fix the problem.
> > 
> > Mimi
> > 
> 
> The error message is coming from ima_pcrread, and the tpm_digest that
> gets passed
> by ima_calc_boot_aggregate_tfm to ima_pcrread is declared:
> 
> 	struct tpm_digest d = { .alg_id = TPM_ALG_SHA1, .digest = {0}
> };
> 
> According to Dell their default BIOS setting is to use sha256. What
> they see with that
> setting is:
> 
> [ 5.475036] ima: Error Communicating to TPM chip
> [ 5.475083] tsc: Refined TSC clocksource calibration: 3311.999 MHz
> [ 5.475092] clocksource: tsc: mask: 0xffffffffffffffff max_cycles:
> 0x2fbd936b72f, max_idle_ns: 440795283163 ns
> [ 5.475118] ima: Error Communicating to TPM chip
> [ 5.475165] ima: Error Communicating to TPM chip
> [ 5.475235] clocksource: Switched to clocksource tsc
> [ 5.475266] ima: Error Communicating to TPM chip
> [ 5.475311] ima: Error Communicating to TPM chip
> [ 5.475341] ima: Error Communicating to TPM chip
> [ 5.475371] ima: Error Communicating to TPM chip
> [ 5.475402] ima: Error Communicating to TPM chip
> [ 5.489049] ima: No architecture policies found

The implication seems to be that on a DELL setting the bios default to
sha256 turns off the TPM's sha1 pcr banks ... is that the case?

tssgetcapability -cap 5

should confirm or deny this.

James


  reply	other threads:[~2020-01-17 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14  0:06 ima pcr question Jerry Snitselaar
2020-01-14  1:17 ` Mimi Zohar
2020-01-17 22:29   ` Jerry Snitselaar
2020-01-17 23:00     ` James Bottomley [this message]
2020-01-18 19:14       ` Jerry Snitselaar
2020-01-18 23:20         ` Jerry Snitselaar
2020-01-18 23:51           ` James Bottomley
2020-01-20  0:13             ` Mimi Zohar

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=1579302011.13499.9.camel@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=jsnitsel@redhat.com \
    --cc=linux-integrity@vger.kernel.org \
    --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.