linux-kernel - Re: [RFC PATCH 0/4] Alternative TPM patches for Trenchboot

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: <11eb20711f597b355c38abfce54ccff7f68fa5c9.camel@HansenPartnership.com>
Date: Mon, 04 Nov 2024 15:36:46 -0500
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: "Daniel P. Smith" <dpsmith@...rtussolutions.com>, Ard Biesheuvel
	 <ardb@...nel.org>
Cc: Jarkko Sakkinen <jarkko@...nel.org>, x86@...nel.org, Ross Philipson
 <ross.philipson@...cle.com>, Thomas Gleixner <tglx@...utronix.de>, Peter
 Huewe <peterhuewe@....de>, Jason Gunthorpe <jgg@...pe.ca>, "open list:TPM
 DEVICE DRIVER" <linux-integrity@...r.kernel.org>, open list
 <linux-kernel@...r.kernel.org>,  trenchboot-devel@...glegroups.com
Subject: Re: [RFC PATCH 0/4] Alternative TPM patches for Trenchboot

On Mon, 2024-11-04 at 11:34 -0500, Daniel P. Smith wrote:
[...]
> In case the question comes up from those not familiar, the kexec does
> an GETSEC[SEXIT] which closes off access to Localities 1 and 2, thus 
> locking the DRTM PCR values. It brings the CPUs out of SMX mode so
> the target kernel does not require to have any knowledge about
> running in that mode.

So, to repeat the question: why a sysfs interface for setting the
default locality?  If I understand correctly from what you say above,
it can't be used in any kernel except the SL one, and that one could
run permanently in it, so there's no requirement at all for user space
to be able to change this, is there?

Regards,

James