linux-kernel - Re: [PATCH v5 2/2] module: Block a module by TUXEDO from accessing GPL symbols

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: <2024111821-gathering-storage-04c3@gregkh>
Date: Mon, 18 Nov 2024 15:03:39 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Daniel Gomez <da.gomez@...sung.com>
Cc: Uwe Kleine-König <u.kleine-koenig@...libre.com>,
	Daniel Gomez <d+samsung@...ces.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Werner Sembach <wse@...edocomputers.com>, mcgrof@...nel.org,
	petr.pavlu@...e.com, samitolvanen@...gle.com,
	linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux@...mhuis.info, vv@...edocomputers.com, cs@...edo.de,
	linux-spdx@...r.kernel.org
Subject: Re: [PATCH v5 2/2] module: Block a module by TUXEDO from accessing
 GPL symbols

On Mon, Nov 18, 2024 at 10:05:27AM +0100, Daniel Gomez wrote:
> Thomas, Greg, are we using any specific SPDX version for kernel license
> identifiers? Why the new identifiers where amended as valid and not
> replacing [2] the old ones? Was it to avoid replacing all files with the
> old id?

Yes it was.  Let's worry about getting all files in the kernel properly
tagged before even considering moving to newer versions of the SPDX
specification.  When we started this, we used the most up to date tags,
but then they changed, and we didn't want to change all of the kernel
while half-way in the middle of the conversion.

Just leave it as-is please.

thanks,

greg k-h