News for hackers. Stuff that matters.
Re:Before you Dual Boot – MS, OEMs and Linux by mindslight on Sunday March 16, 2014 @07:52PM (#7411990)
The idea of secure boot could theoretically be a no-tradeoff security positive, but the implementation would be quite different from what it is currently. For starters, any non-user-hostile solution is going to have something like a usb device header on the motherboard as the highest-privileged interface to the system (with something like mandatory time delays to prevent against evil maid attacks). But to large manufacturers run by business people, the attraction to a hardcoded manufacturer-administered signing certificate for the trust root (which obviously erodes the owner's control) is just too strong for us to see a proper implementation any time soon.
Re:Before you Dual Boot – MS, OEMs and Linux by comex on Monday March 17, 2014 @01:05AM (#7413178)
You realize that with UEFI (ed: on x86... yes, Windows RT devices are different), you can either disable Secure Boot or (at least on some systems) replace the root key with your own, without any hardware modification?

On Chromebooks, which I'm a bit more familiar, you cannot, and disabling verification involves a 30 second delay on boot with beep, to prevent against evil maid attacks. However, apparently it's not too hard [1] to flash the ROM on some devices if you can open the thing.

[1] http://krblogs.com/post/63809988096/bootloader-unlock-on-sam...

Re:Before you Dual Boot – MS, OEMs and Linux by yuhong on Sunday March 16, 2014 @09:09PM (#7412285)
I once proposed handing the keys to an independent standard body, particularly after FSF complained about the process.
Re:Before you Dual Boot – MS, OEMs and Linux by mindslight on Sunday March 16, 2014 @09:38PM (#7412380)
But why forge a centralized ring of power in the first place? Even completely above-reproach independent bodies can still be co-opted by subpoenas and the like. And the mere existence of that possibility for control is blood in the water for governments.