Those Who Helped Microsoft Weaponise "Secure Boot" Against GNU/Linux and BSDs Are Fleeing

posted by Roy Schestowitz on Sep 09, 2025

Microsofters doing what they do best: they evade accountability

Whilst away in another timezone one can see the clock showing 9/10 (or 10/9, depending on the date formatting conventions). That means that tomorrow is UEFI 9/11^*.

Yesterday we published "If Your Machine Still Has "Secure Boot" Enabled, Then Microsoft Has a de Facto Kill Switch (Even If Your Machine Doesn't Have Windows and Never Had Windows)" and we'll soon conclude the series, then start another new series - one about the aftermath.

"Secure Boot" was never about security; it was trouble all along, going back to 2011. GNU/Linux users resisted this injustice, but Microsofters resisted these users and now escape the (metaphorically) "scene of the crime":

Always pretending to be away when doing terrible things [1, 2]. █

_____________

^* Ongoing series:

1. The UEFI 9/11 - Part I - Introduction to Impending Catastrophe (Microsoft Preventing People From Booting Non-Windows Systems)
2. The UEFI 9/11 - Part II - Campaign of Censorship and Defamation Against Critics
3. The UEFI 9/11 - Part III - Chaos is Scheduled to Happen Second Thursday of September (No Matter What the Microsofters Tell You)
4. The UEFI 9/11 - Part IV - External Interference
5. The UEFI 9/11 - Part V - This is Not a Drill (Disable "SecureBoot" Now)
6. The UEFI 9/11 - Part VI - This Serious Harm Was Planned for Over a Decade, Not an Accident or Merely Some Misfortune
7. The UEFI 9/11 - Part VII - This Coming Week Many PCs Will Refuse to Boot "Linux" (Because of Microsoft's Expired Certificate)
8. The UEFI 9/11 - Part VIII - Denial of Service and Selling Us WSL (Windows) Instead of "Risky" (Prone by Breakage by Microsoft) GNU/Linux
9. The UEFI 9/11 - Part IX - Shunning Old Computers (in 2023 the Certificate Was Updated/Overridden, Underlying Aim May Be Herding/Forcing People to Get TPM and Other 'Novel' Restrictions)