linux-kernel - Re: [PATCH] efi: expose TPM event log to userspace via sysfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <6e751959b9056884c1b9d3ba23e303d1737d8763.camel@HansenPartnership.com>
Date: Mon, 22 Apr 2024 08:42:41 -0400
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Mikko Rapeli <mikko.rapeli@...aro.org>, Ard Biesheuvel
 <ardb@...nel.org>,  linux-efi@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, Ilias Apalodimas
 <ilias.apalodimas@...aro.org>,  Lennart Poettering <lennart@...ttering.net>
Subject: Re: [PATCH] efi: expose TPM event log to userspace via sysfs

On Mon, 2024-04-22 at 14:27 +0300, Mikko Rapeli wrote:
> Userspace needs to know if TPM kernel drivers need to be loaded
> and related services started early in the boot if TPM device
> is used and available.

This says what but not why.  We already have module autoloading that
works correctly for TPM devices, so why is this needed?

We do have a chicken and egg problem with IMA in that the TPM driver
needs to be present *before* any filesystem, including the one the TPM
modules would be on, is mounted so executions can be measured into IMA
(meaning that if you use IMA the TPM drivers must be built in) but this
sounds to be something different. However, because of the IMA problem,
most distributions don't end up compiling TPM drivers as modules
anyway.

Is what you want simply that tpm modules be loaded earlier?

James