Windows 8 Secure Boot Defeated
jhigh writes "An Austrian security researcher is scheduled to release the first 'bootkit' for Windows 8 at the upcoming MalCon in Mumbai. This exploit loads in the MBR and stays memory resident until Windows loads, resulting in root access to the system. This allegedly defeats the new secure boot features in Windows 8's bootloader."
But if the Windows bootloader integrity is compromised, we could all end up infected with Ubuntu, Debian, FreeBSD--god only knows what!
Won't someone PLEASE think of the children?!?!?
SJW: Someone who has run out of real oppression, and has to fake it.
Secure Boot is a UEFI feature, not Windows one. The article makes no reference to UEFI whatsoever - and it offers no explanation either for what mechanic was actually defeated. I do doubt the integrity of the article ARS is using.
Finally a jailbreak for the desktop! I was tired of using locked-down hardware! I will now run a jailbroken desktop exclusively.
Uhh UEFI literally has no MBR, it doesn't exist. So please explain to me how this exploit functions when the MBR doesn't exist? I think he is booting his drives in the wrong mode, which is to say legacy MBR mode instead of ADAPI/UEFI mode.
This would have been solved sooner if Modern Warfare 3 hadn't been released last week...
I thought the point to the UEFI secure boot thing was that the UEFI wouldn't boot without the MBR and remainder of the boot blocks being properly digitally signed.
Unless someone broke the digital signature system or found a flaw in the implementation, this sounds more like working as intended.
The article also seems to think that the boot loader is supposed to be encrypted for some silly reason.
Seems pretty clear that the article doesn't understand how it works, so its hard to imagine theres much truth in it. If you tell the UEFI to ignore digital signatures on the boot loader then yes, it has been compromised ... cause you turned it off. Intentionally turning it off doesn't count as breaking it guys, sorry.
If there was a claim of a flaw in the UEFI Secure boot implementation or design, then I'd listen, but the fact that its being called a windows exploit when it occurs before Windows has been started kinda sets off signal flares, ya know?
Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
Without a UEFI computer that is configured to boot only signed boot-loaders, this is not a valid test of the Secure Boot technology.
Basically, this is a case of "of course it works that way in this scenario, it's supposed to."
Knowledge is how to play a game, intelligence is how to win, wisdom is knowing what game to play.
Seriously, hello, editors? Is anybody home? This post is 100% false. The very subject of this story has tweeted:
No it's not attacking UEFI or secure boot, right now working with the legacy BIOS only (details will be in the paper)
Do the words "reckless disregard for the truth" have any meaning to you?
If you don't know where you are going, you will wind up somewhere else.