Some Linux users might be interested, reading about this (Subscriber link, that bypasses the Paywall, since I find this information important to spread for awareness):

https://lwn.net/SubscriberLink/1029767/0a550f0972703141/

„Linux users who have Secure Boot enabled on their systems knowingly or unknowingly rely on a key from Microsoft that is set to expire in September. After that point, Microsoft will no longer use that key to sign the shim first-stage UEFI bootloader that is used by Linux distributions to boot the kernel with Secure Boot. But the replacement key, which has been available since 2023, may not be installed on many systems; worse yet, it may require the hardware vendor to issue an update for the system firmware, which may or may not happen.“

#linux #secureboot #microsoft #security #servicetweet

Linux and Secure Boot certificate expiration

Linux users who have Secure Boot enabled on their systems knowingly or unknowingly rely on a ke [...]

LWN.net
@Larvitz And that's why "secure boot" is bullshit and has always been part of planned obsolescence
@howtophil @Larvitz you're supposed to install updates from time to time, you know?

@voice @Larvitz @howtophil except if you use anything other than Windows, firmware updates have a tendency to just break a bunch of shit, especially if you’re in a situation like me and had to enable debug settings and change options I’m not supposed to even see just to get my laptop working properly with Linux

like, trust me, I actually avoid installing any UEFI updates for no reason other than “everything UEFI on this laptop is built on a house of cards that an UEFI update is likely to wreck”

@Reiddragon @Larvitz @howtophil afaik certificates and revocation lists are separate from the firmware updates, but not really sure because using SB with microsoft third party ca is pointless anyway.

This is sad. And also one of reasons, why I use only Latitudes in the past and Thinkpads now.