4 ms·
As someone who isn't versed in computer hardware engineering, can nothing be done here? Why is it there is a new backdoor every few months? Is it an architectur
by tomrod 6y ago
As someone who isn't versed in computer hardware engineering, can nothing be done here? Why is it there is a new backdoor every few months? Is it an architecture issue, and we simply demand too much for too cheap? How do we lock this down?
- jeffbee 6y agoThis post is a nothing-burger. That an instruction exists that permits microcode updates is not new knowledge. Obviously there is one, if you can update microcode. All that's new here is reverse-engineering has filled in one of the holes in the Intel SDM.
- monocasa 6y agoThe previous publicly known mechanism required signed updates. This mechanism allows anyone to twiddle the bits.
- usr1106 6y ago> This mechanism allows anyone to twiddle the bits. This remained unclear to me. Other comments say the CPU needs to be in red unlocked state, whatever that is. The screenshot shows UEFI. So one could guess the CPU is in such state before the operating system gets loaded. But the operating system typically loads a microcode update, after that the CPU should no longer be in unlocked state. So for "everyone can fiddle with the bits", that would require to run a modified bootloader first. Which should not be possible thanks to secure boot. So yes, maybe it's a small step to another highly complex exploit. But it's not that everybody running a securely booted operating system (which should be everybody) can start fiddling with bits. Edit: There is a difference between your own bits and someone else's bits. Yes, on your own machine you can run a modified bootloader and that's a good thing. Putting a modified bootloader to another machine should not be possible (until someone breaks secure boot, but I don't think that has publicly happened)
- tinus_hn 6y agoIf you’re not doing this as a hack but to get more control over your own processor, you can just turn off secure boot, it’s a bios setting.
- floatboth 6y agoFirmware is not protected by Secure Boot. It can be protected by things like Boot Guard, but at least that one (Intel's) requires pairing the board and the CPU, so it can only be done in laptops and other prebuilt OEM systems.
- usr1106 6y agoWhat do you mean by firmware here? Microcode? No it's not. But as long as you only load bootloaders or operating systems that are signed, it doesn't matter that they could fiddle with the bits as long as the signature guarantees they don't (in any undesired way). Or ME? Well, that seems to be a complete security nightmare.
- floatboth 6y agoMicrocode is protected by its own signing thing, IIUC. Firmware is both ME firmware and x86 firmware — the UEFI implementation, FSP, everything else that runs on early boot.
- 6y ago