Reader blames Microsoft's Secure Boot handling
2 Nov 3 11:13 AM · 4d ago · 1 post · 1 source · development 2 of 2
A Mastodon reader responding to the Ars Technica report argued the recurring Secure Boot failures point squarely back to Microsoft.
“The answer to "is Microslop to blame?" is always, inevitably, yes...”
kim_harding@mastodon.scotMicrosoft Windows and Secure Boot vendorBlackLotus Precedent UEFI bootkit (2023)BlackX Newly identified UEFI bootkit
The whole story articlesposts the bright band is this development · numbered dots are the others · click one to jump
What people said 1 voice · best of 4 · verbatim
-
M
https:// arstechnica.com/security/2026/ 11/uefi-bootkit-infected-fully-patched-windows-machines-is-microsoft-to-blame/ calls to mind something I wrote back in 2022: https:// mjg59.dreamwidth.org/60248.html . Systems are vulnerable to UEFI secure boot bypasses because Microsoft refuses to revoke their old bootloaders by default, because that would…
All 2 developments of New UEFI bootkit BlackX bypasses Secure Boot on fully… →
MastodonNewswiresGoogle NewsBluesky