From: "Lendacky, Thomas" <thomas.lendacky@amd.com>
To: devel@edk2.groups.io, public@thson.de,
James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: lersek@redhat.com, ardb+tianocore@kernel.org
Subject: Re: [edk2-devel] Problem: TPM 2.0 event log by OVMF is shown empty in Linux kernel versions after 5.8
Date: Tue, 27 Apr 2021 09:00:48 -0500 [thread overview]
Message-ID: <2e82d24c-2cf2-1681-646d-3f848818ade8@amd.com> (raw)
In-Reply-To: <76f91d91-9eb9-3e31-b09b-3ecfc0c03a4f@thson.de>
On 4/27/21 2:40 AM, Thore Sommer via groups.io wrote:
>
>> I don't confirm this. I have Linux version 5.12.0-rc5+ installed and I
>> see the attached in my binary_bios_measurements (I've run it through
>> tpm2-eventlog so you can see the actual events).
> Ok that is interesting.
>
> Here are the steps to reproduce my findings.
> Necessary tools: Build chain for edk2, swtpm 0.5.2 and qemu 5.2.0
>
> 1. Build OVMF from edk2-stable202102 with
> -a X64 -a IA32 \
> -b RELEASE \
> -D NETWORK_IP6_ENABLE \
> -D TPM_ENABLE \
Shouldn't you also have '-D TPM_CONFIG_ENABLE' ?
Thanks,
Tom
> -D FD_SIZE_4MB \
> -D TLS_ENABLE \
> -D HTTP_BOOT_ENABLE \
> -D SECURE_BOOT_ENABLE \
> -D SMM_REQUIRE \
> -D EXCLUDE_SHELL_FROM_FD
>
> 2. Copy OVMF_CODE.fd and OVMF_VARS.fd into an empty directory
> 3. Download Ubuntu 21.04 desktop iso (which has a 5.11 Linux kernel) and
> copy it into that directory
> (I can provide a custom Debian build with a patched and unpatched vanilla
> kernel if needed)
> 4. Create dir for swtpm: mkdir mytpm1
> 5. Start swtpm with
> swtpm socket \
> --tpm2 \
> --tpmstate dir=mytpm1 \
> --ctrl type=unixio,path=mytpm1/swtpm-sock \
> --log level=4 &
> 6. Start qemu with
> qemu-system-x86_64 \
> -enable-kvm \
> -machine q35,smm=on \
> -global driver=cfi.pflash01,property=secure,value=on \
> -drive if=pflash,format=raw,unit=0,file=OVMF_CODE.fd,readonly=on \
> -drive if=pflash,format=raw,unit=1,readonly=off,file=OVMF_VARS.fd \
> -chardev socket,id=chrtpm,path=mytpm1/swtpm-sock \
> -tpmdev emulator,id=tpm0,chardev=chrtpm \
> -device tpm-crb,tpmdev=tpm0 \
> -boot d \
> -cdrom "ubuntu-21.04-desktop-amd64.iso" \
> -m 3G \
> -vga virtio
> 7. Start Ubuntu normally and choose "Try Ubuntu"
> 8. Open a Terminal and check that
> "/sys/kernel/security/tpm0/binary_bios_measurements" is empty
>
>> On my OVMF boot I'm using the direct
>> kernel command line and I have secure boot enabled but not activated,
>> which is why you only see PCRs 0-7 in the log.
>
> The Kernel here is loaded by Grub which itself is loaded by Shim. But that
> should not make a difference regarding the event log via ACPI right?
>
> I've attached the event log from a Ubuntu 20.04 machine with a 5.12
> patched kernel and my kernel build config.
>
> Best regards
> Thore Sommer
>
>
>
>
>
next prev parent reply other threads:[~2021-04-27 14:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 19:56 Problem: TPM 2.0 event log by OVMF is shown empty in Linux kernel versions after 5.8 Thore Sommer
2021-04-26 23:44 ` [edk2-devel] " James Bottomley
2021-04-27 7:40 ` Thore Sommer
2021-04-27 14:00 ` Lendacky, Thomas [this message]
2021-04-27 15:35 ` Thore Sommer
2021-04-27 16:28 ` James Bottomley
2021-04-28 11:47 ` Laszlo Ersek
2021-04-28 14:56 ` Thore Sommer
2021-04-28 17:19 ` James Bottomley
2021-04-28 20:31 ` Thore Sommer
2021-04-28 22:03 ` James Bottomley
2021-04-29 8:20 ` Thore Sommer
2021-04-29 9:43 ` Thore Sommer
2021-04-30 15:51 ` Laszlo Ersek
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-list 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=2e82d24c-2cf2-1681-646d-3f848818ade8@amd.com \
--to=devel@edk2.groups.io \
/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