linux-integrity.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>,
	Mimi Zohar <zohar@linux.ibm.com>,
	linux-integrity@vger.kernel.org
Subject: Re: ima pcr question
Date: Sat, 18 Jan 2020 15:51:40 -0800	[thread overview]
Message-ID: <1579391500.3421.35.camel@HansenPartnership.com> (raw)
In-Reply-To: <20200118232004.lt2u2u6ryitrkaa2@cantor>

On Sat, 2020-01-18 at 16:20 -0700, Jerry Snitselaar wrote:
> On Sat Jan 18 20, Jerry Snitselaar wrote:
> > On Fri Jan 17 20, James Bottomley wrote:
[...]
> > > 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
> > > 
> > 
> > I believe so, I'm waiting to get access to the system here to
> > double check. Before with the intel stack, tpm2_pcrlist -s would
> > return both sha1 and sha256, but the plain tpm2_pcrlist command
> > would show only banks for one or the other depending on which
> > setting was in the bios. For the other it would just print
> > out the algorithm and nothing else.
> > 
> > I should be able to run the tss2 command later today.
> > 
> > Regards,
> > Jerry
> 
> with sha1 selected:
> 
> [root@dell-per830-01 ~]# tssgetcapability -cap 5
> 2 PCR selections
>      hash TPM_ALG_SHA1
>      TPMS_PCR_SELECTION length 3
>      ff ff ff 
>      hash TPM_ALG_SHA256
>      TPMS_PCR_SELECTION length 3
>      00 00 00 
> 
> with sha256 selected:
> 
> [root@dell-per830-01 ~]# tssgetcapability -cap 5
> 2 PCR selections
>      hash TPM_ALG_SHA1
>      TPMS_PCR_SELECTION length 3
>      00 00 00 
>      hash TPM_ALG_SHA256
>      TPMS_PCR_SELECTION length 3
>      ff ff ff 

OK, so that confirms the suspicion.  The only active bank is the one
you've selected in the bios ... I suppose it was done to avoid having
to measure through more than one bank, but it does mean IMA must cope
in the case the sha1 bank isn't active.

James


  reply	other threads:[~2020-01-18 23:51 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
2020-01-18 19:14       ` Jerry Snitselaar
2020-01-18 23:20         ` Jerry Snitselaar
2020-01-18 23:51           ` James Bottomley [this message]
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=1579391500.3421.35.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 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).