Avoid the Hack! Aug 26, 2024

Not sure if anyone else has mentioned this, but wanted to add a specific data point to the #Linux and #Windows dualboot problem: it affects USB installs too. Makes sense it covers all bootable media, but experiencing it firsthand kind of sucked. Kind of a doh moment. 

I have live #Kali and #tails sticks that won’t boot on the Windows machine (get the SBAT error).

Disabling Secure Boot allows it to boot (naturally, it will also boot if I plug it into my Linux machine). The temporary fix from #Microsoft does work. As a note for TAILS users, you can’t run mokutils as sudo (which is needed) unless you enable setting administrator password on boot.

#secureboot

Show threadgary
@avoidthehack easy workarounds for this are to boot from separate media - just change boot order in bios or virt where you can run everything concurrently with enough ram and cores #bootloader specs #crickets #uefi #secure boot #tpm #pkfail #badbios
Aug 26, 2024 at 6:09pmWeb
Show threadAvoid the Hack! Aug 26, 2024

@gary_alderson No. That's precisely the issue in this instance; any boot media using GRUBv2 (as far as I know) will get the SBAT violation, the machine will not boot into the media/OS attached to the machine without a fix for CVE-2022-2601… it just won’t boot with Secure Boot enabled (after installing the August 2024 Windows updates).

Virtualization is kind of irrelevant here - especially if you had a Linux install on a separate media but attached to the Windows machine. Sure, you could set up a virtualization environment after loading into Windows, but leaves people wanting to use Live OS or boot into a whole separate OS on that machine in the dust.