What is an SBAT and why does everyone suddenly care
Secure Boot Advanced Targeting (SBAT) simplifies boot security for dual-boot systems by using security generations. Recent Microsoft updates marked older GRUB versions untrustworthy, raising concerns about user access and update testing.
Read original articleThe article discusses the recent emergence of Secure Boot Advanced Targeting (SBAT) and its implications for dual-boot systems, particularly those running Windows and Linux. SBAT was developed to address vulnerabilities in bootloaders, specifically the GRUB bootloader, which is used by many Linux distributions. The traditional Secure Boot model required revoking individual hashes of untrustworthy code, which became impractical due to storage limitations. SBAT simplifies this by allowing boot components to declare a security generation, which can be incremented when vulnerabilities are fixed. Microsoft recently pushed an update that marked older versions of GRUB as untrustworthy, leading to boot failures for some dual-boot systems that had not updated their GRUB versions. This situation has raised concerns about the testing and deployment of updates, as well as the responsibility of Linux distributions to ensure their bootloaders are secure. The article emphasizes the need for better communication and testing to prevent end users from being locked out of their systems due to security updates.
- SBAT simplifies the Secure Boot process by using security generations instead of individual hashes.
- Microsoft's update marked older GRUB versions as untrustworthy, affecting dual-boot systems.
- The situation highlights the need for better testing of updates to avoid user lockouts.
- Linux distributions must ensure their bootloaders are updated to maintain security.
- The incident raises questions about the balance between security and user accessibility.
Related
Tell HN: Microsoft SecureBoot "Breaking" Changes, Today's Milestone
Microsoft's Patch Tuesday updates KB5041585 and KB5041580 for Windows 10 and 11 fix boot issues with older Linux ISO images and automatically blacklist compromised SecureBoot keys, excluding dual-boot systems.
Dual-boot systems fail after Microsoft update
Microsoft's update to fix a GRUB vulnerability caused boot failures in dual-boot systems, affecting Linux distributions. Users reported issues, and Microsoft has not acknowledged or provided support for the problem.
Microsoft's latest security update has ruined dual-boot
Microsoft's security update has disrupted dual-boot systems with Windows and Linux, causing boot issues and error messages. A workaround for Ubuntu users involves disabling Secure Boot in the BIOS.
“Something has gone seriously wrong,” dual-boot systems warn after MS update
Microsoft's update to fix a GRUB vulnerability has caused boot failures in dual-boot systems, affecting Linux distributions like Debian and Ubuntu, while raising concerns about Secure Boot's reliability and security.
Microsoft's latest security update has ruined dual-boot Windows and Linux PCs
Microsoft's security update has disrupted dual-boot systems with Windows and Linux, causing boot issues and error messages. A workaround exists for Ubuntu users, highlighting vulnerabilities in Secure Boot technology.
"trustworthy" according to who? Remember that dystopia does not appear spontaneously, but steadily advances little-by-little.
What's the summary? Microsoft (understandably) didn't want it to be possible to attack Windows by using a vulnerable version of grub that could be tricked into executing arbitrary code and then introduce a bootkit into the Windows kernel during boot. Microsoft did this by pushing a Windows Update that updated the SBAT variable to indicate that known-vulnerable versions of grub shouldn't be allowed to boot on those systems.
Who is Microsoft to decide what others do on their machines? Should they have the right to police and censor software they have no control of? In the spirit of Linus Torvalds: Microsoft, fuck you!
We are seeing the scenario Stallman alluded to over 2 decades ago slowly become a reality. He wasn't alone either.
https://www.gnu.org/philosophy/right-to-read.en.html
https://www.cl.cam.ac.uk/~rja14/tcpa-faq.html
Things like TPM and "secure" boot were never envisioned for the interests of the user. The fact that it incidentally protects against 3rd party attacks just happened to be a good marketing point.
"Those who give up freedom for security deserve neither."
[0] https://linuxunplugged.com/572
[1] https://fedoramagazine.org/automatically-decrypt-your-disk-u...
I wonder what went wrong here? If you would read the EFI boot order it would clearly say to boot shim first? Or were these dual boot setups where the user would use the firmware menu to select linux or windows?
Anyway this comes at a time when I want to install linux on my work PC, since it has two nvme slots I think I'll go with installing it on a completely separate drive. Would have not prevented this issue though, which seems a legitimate fix from microsoft, just bad communication.
When it comes to the realities of dual-booting, I had tons of problems with Win7/8/10 with suspend-to-hiberfile.sys issues and updates 10 years ago breaking grub. 10 years ago I finally decided, "You know what, I'm just going to run Linux, if I really need Windows or Mac, I can run a VM or use a separate spare computer."
Since then I have successfully setup Secure Boot for my distro, learned how to tweak QEMU for performance and passthrough, got a working QEMU macOS VM (although having to update every few months to keep XCode working is a pain), and generally pretty happy with the state of affairs.
I see the end of the chain still ends up at "trust" in humans/companies at some level. Microsoft broke dual boot systems because they think they know what's best for someone else's system and that's not okay.
I'd be also really curious to hear how MS was attempting to do dual-boot detection, I hope someone (more skilled than I) would reverse engineer that bit from the update.
The fact that the list of allowed GRUB versions is itself manageable via a Windows Update points to some other issues with this particular security scheme, given Microsoft’s own recent history of mishandling private keys.
* No matter how many times I do the captcha.
> those versions of grub had genuine security vulnerabilities that would allow an attacker to compromise the Windows secure boot chain
This feels like a "my secure compartments are all connected together" moment. If Microsoft want to verify that they're in an all-Microsoft boot chain, sure, whatever, fine. But somehow the compromise of any loader allows compromise of Windows? And in turn Microsoft are able to break grub installations? Why is that acceptable?
(also, I feel a bit "I told you so" about this. Back when all this was being introduced I felt that (a) secure boot increases the risk of locking you out of your machine and/or data loss and (b) a situation where Linux is dependent on the collaboration of Microsoft in order to boot is very dangerous long-term.)
You can buy a computer with Linux installed, today!
Ubuntu is easy, so is kubuntu.
You can do anything on Linux that you can do on windows and most of the time it's child's play. The past is the past, give up on windows.
Now I always google around a bit before applying any fresh Windows updates to see of there's any breakage reported.
Ive never been sucessfully able to dual boot windows and linux on a mobo with secure boot turned on, it seems that is a feature not a bug I'm sure MS would never influence hardware vendors to make it dissadvantage a growing number of linux users.
Based. Unfathomably based.
https://www.sportskeeda.com/pop-culture/who-hudson-mohawke-d...
Related
Tell HN: Microsoft SecureBoot "Breaking" Changes, Today's Milestone
Microsoft's Patch Tuesday updates KB5041585 and KB5041580 for Windows 10 and 11 fix boot issues with older Linux ISO images and automatically blacklist compromised SecureBoot keys, excluding dual-boot systems.
Dual-boot systems fail after Microsoft update
Microsoft's update to fix a GRUB vulnerability caused boot failures in dual-boot systems, affecting Linux distributions. Users reported issues, and Microsoft has not acknowledged or provided support for the problem.
Microsoft's latest security update has ruined dual-boot
Microsoft's security update has disrupted dual-boot systems with Windows and Linux, causing boot issues and error messages. A workaround for Ubuntu users involves disabling Secure Boot in the BIOS.
“Something has gone seriously wrong,” dual-boot systems warn after MS update
Microsoft's update to fix a GRUB vulnerability has caused boot failures in dual-boot systems, affecting Linux distributions like Debian and Ubuntu, while raising concerns about Secure Boot's reliability and security.
Microsoft's latest security update has ruined dual-boot Windows and Linux PCs
Microsoft's security update has disrupted dual-boot systems with Windows and Linux, causing boot issues and error messages. A workaround exists for Ubuntu users, highlighting vulnerabilities in Secure Boot technology.