linux-kernel - Re: [PATCH v14 00/19] x86: Trenchboot secure dynamic launch Linux kernel support

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] [day] [month] [year] [list]

Message-ID: <CAAyYeYjp0v2PYt1owTdOpQD8_NjakquyXbUr5M1a_OWLEKHQ0A@mail.gmail.com>
Date: Sun, 18 May 2025 09:42:23 -0500
From: Mike <mikewallacesmith90@...il.com>
To: Dave Hansen <dave.hansen@...el.com>
Cc: "Daniel P. Smith" <dpsmith@...rtussolutions.com>, Rich Persaud <persaur@...il.com>, 
	Ross Philipson <ross.philipson@...cle.com>, linux-kernel@...r.kernel.org, x86@...nel.org, 
	linux-integrity@...r.kernel.org, linux-doc@...r.kernel.org, 
	linux-crypto@...r.kernel.org, kexec@...ts.infradead.org, 
	linux-efi@...r.kernel.org, iommu@...ts.linux.dev, tglx@...utronix.de, 
	mingo@...hat.com, bp@...en8.de, hpa@...or.com, dave.hansen@...ux.intel.com, 
	ardb@...nel.org, mjg59@...f.ucam.org, James.Bottomley@...senpartnership.com, 
	peterhuewe@....de, jarkko@...nel.org, jgg@...pe.ca, luto@...capital.net, 
	nivedita@...m.mit.edu, herbert@...dor.apana.org.au, davem@...emloft.net, 
	corbet@....net, ebiederm@...ssion.com, dwmw2@...radead.org, 
	baolu.lu@...ux.intel.com, kanth.ghatraju@...cle.com, 
	andrew.cooper3@...rix.com, trenchboot-devel@...glegroups.com, 
	Sergii Dmytruk <sergii.dmytruk@...eb.com>, openxt@...glegroups.com, 
	"Mowka, Mateusz" <mateusz.mowka@...el.com>, Ning Sun <ning.sun@...el.com>, 
	tboot-devel@...ts.sourceforge.net
Subject: Re: [PATCH v14 00/19] x86: Trenchboot secure dynamic launch Linux
 kernel support

On Mon, Apr 28, 2025 at 7:57 PM Dave Hansen <dave.hansen@...el.com> wrote:
>
> On 4/28/25 17:04, Daniel P. Smith wrote:
> >> OK, but why do this in Linux as opposed to tboot? Right now, much of the
> >> TXT magic is done outside of the kernel. Why do it *IN* the kernel?
> >
> > There was a patch set submitted to tboot to add AMD support. It was
> > rejected as tboot is solely focused on Intel TXT implementation.
> >
> > This meant I either had to go the route of yet another standalone loader
> > kernel or do it in the kernel. Doing it as an external loader would have
> > required a new set of touchpoints, like the one you are highlighting. At
> > which point, I am sure I would have gotten the question of why I didn't
> > do it in the kernel.

Will this cause any patent infringement issues in Linux [1]?

1. https://patents.google.com/patent/US9075995B2