Resolution: Microsoft should be held liable for failing to revoke compromised Secure Boot certificates for a decade.
Fact sheet
- Microsoft's Secure Boot feature contained a vulnerability for approximately ten years - The vulnerability involved old "shims" that Microsoft did not revoke - These unrevoked shims enabled bypasses of Secure Boot security measures - The security issue went undetected until recently - Secure Boot is designed to prevent unauthorized software from loading during system startup
Bracket