public inbox for linux-integrity@vger.kernel.org
 help / color / mirror / Atom feed
From: Francesco Dolcini <francesco@dolcini.it>
To: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Hermin Anggawijaya <hermin.anggawijaya@alliedtelesis.co.nz>,
	peterhuewe@gmx.de, jgg@ziepe.ca, linux-integrity@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tpm: Start the tpm2 before running a self test.
Date: Mon, 15 Jul 2024 19:39:05 +0200	[thread overview]
Message-ID: <20240715173905.GA81987@francesco-nb> (raw)
In-Reply-To: <CX6NSGFJVYKC.3KFEPA92N0V53@kernel.org>

Hello Jarkko and all,
resurrecting this old thread for a question ...

On Fri, Nov 24, 2023 at 03:42:29AM +0200, Jarkko Sakkinen wrote:
> On Wed Nov 22, 2023 at 8:55 AM EET, Hermin Anggawijaya wrote:
> > Before sending a command to attempt the self test, the TPM
> > may need to be started, otherwise the self test returns
> > TPM2_RC_INITIALIZE value causing a log as follows:
> > "tpm tpm0: A TPM error (256) occurred attempting the self test".
> >
> > Signed-off-by: Hermin Anggawijaya <hermin.anggawijaya@alliedtelesis.co.nz>
> 
> Firmware does TPM power on.

Do you have any explanation on why this is required? Any kind of pointer
to documentation is welcome.

What I am looking for is to understand what are the major limitations if
the firmware is not doing it.

I understand that you cannot use any functionality that requires the TPM
to be enabled at boot, for example "Measured Boot". Is there anything
else that is prevented if the firmware is not enabling it?

Thanks,
Francesco


      parent reply	other threads:[~2024-07-15 17:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22  6:55 [PATCH] tpm: Start the tpm2 before running a self test Hermin Anggawijaya
2023-11-22  7:10 ` Paul Menzel
2023-11-26 21:16   ` Angga
2023-11-22 12:34 ` Stefan Berger
2023-11-27  2:02   ` Angga
2023-12-04  2:36     ` Jarkko Sakkinen
2023-11-24  1:42 ` Jarkko Sakkinen
2023-11-27  2:07   ` Angga
2024-07-15 17:39   ` Francesco Dolcini [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=20240715173905.GA81987@francesco-nb \
    --to=francesco@dolcini.it \
    --cc=hermin.anggawijaya@alliedtelesis.co.nz \
    --cc=jarkko@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-integrity@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterhuewe@gmx.de \
    /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