linux-kernel - Re: [PATCH] platform/x86/intel/ifs: Update documentation to match current availability of firmware images

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: <eeb29cef-fb07-4bf9-9728-346a697ceff1@intel.com>
Date: Thu, 2 Jan 2025 13:40:23 -0800
From: "Joseph, Jithu" <jithu.joseph@...el.com>
To: Anisse Astier <anisse@...ier.eu>, <platform-driver-x86@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
CC: Ashok Raj <ashok.raj.linux@...il.com>, Tony Luck <tony.luck@...el.com>,
	Hans de Goede <hdegoede@...hat.com>, Ilpo Järvinen
	<ilpo.jarvinen@...ux.intel.com>
Subject: Re: [PATCH] platform/x86/intel/ifs: Update documentation to match
 current availability of firmware images



On 1/2/2025 11:43 AM, Anisse Astier wrote:
> Firmware images necessary for the In-field scan[1] functionality are not
> available at the moment[2], and require having access to at least an
> Intel customer account[3].
> 
> Update documentation to match current state, it can be updated again
> when the images are finally published.
> 
> [1] https://www.intel.com/content/www/us/en/support/articles/000099537/processors/intel-xeon-processors.html
> [2] https://cdrdv2.intel.com/v1/dl/getContent/826383?explicitVersion=true
> [3] https://www.intel.com/content/www/us/en/secure/design/confidential/software-kits/kit-details.html?kitId=815180
> 
> Signed-off-by: Anisse Astier <anisse@...ier.eu>
> ---
> I realize Intel had a few troubled years, and that having this feature
> in the kernel must be quite helpful to some users. But right now, it
> cannot be used unless one has a commercial relationship with Intel.
> 
> I am not advocating for the removal of this driver; this is just an
> update of the documentation to show that the publication of the firmware
> images necessary to use the driver might have fallen through the cracks,
> and might not happen soon.

Thanks for bringing this up ... apologies for the delay in making the images publicly available.
We have reached out to internal teams to speed this up.

I will update the the documentation (or respond here) when I have more info

In the meantime, I am okay with updating the documentation  to reflect the current state of image availability


Thanks
Jithu