4 ms·
Whether it's intentional or not, I like that there are still companies which are willing to subvert the corporate authoritarianism of Big Tech. What's funny is
by userbinator 4y ago
Whether it's intentional or not, I like that there are still companies which are willing to subvert the corporate authoritarianism of Big Tech.
What's funny is that "Allow Execute" and "Query User" options are breaking UEFI specification
They're giving the user freedom, which the specification is against. IMHO they chose the right path. Willful disobedience applies to software too. My opinion of MSI just got a little better.
- dawidpotocki 4y agoNo, the specification is not against user freedom. "Always Execute" is not against the spec. "Query User" is partially broken, so it's not even that useful. If you use a bootloader, you will only be able to confirm booting of the bootloader, you won’t be able to confirm the OS that it starts. You will get the dialog, but the input won’t work. MSI did not add any of these features, they are available in EDK II. https://github.com/tianocore/edk2/blob/9ce09870e721efacc41fa7ee684e9e299f120350/SecurityPkg/SecurityPkg.dec#L267-L278 https://github.com/tianocore/edk2/blob/9ce09870e721efacc41fa...
- Conan_Kudo 4y agoAt one point, I would have agreed with you. But Microsoft and Intel have been strong-arming implementations to reduce or eliminate user freedom over the past few years. It's been a sad state of affairs.
- Randor 4y agoThe modes "Allow Execution" at 0x2 and "Query User" at 0x5 are both documented in the UEFI security spec.
- drdaeman 4y agoI hope that they provide a visible warning that secure boot is subverted. So it's not that some evil maid could replace the boot chain and update the firmware settings to make it behave as if nothing happened. Just for those folks who use and want it. And maybe also introduce a TOFU model i.e. "allow execute" but ask when the hash changes, so booting the same unsigned binary is OK but updates aren't silently allowed and require a quick confirmation (possibly with a timer for unattended reboots). Won't help against physical attacker but should help against a malware that manages to get root and tries to install itself into the boot chain.
- stefan_ 4y agoSo the maid replaces your keyboard instead. There is no security in this scenario, the only option is "don't use the computer". Meanwhile, there is a really weird segment of "security people" that focus a whole lot about attestation and signatures and "secure boot" and the like but very little about what actually ends up breaking systems. Call it the Sony syndrome where you ship 15 layers of chainloaded bootloaders and security systems but don't bother updating the years old WebKit. Apple has it too, always money around for implementing another mitigation scheme in XNU but if you ask why nobody updated the outdated open-source PDF library embedded in their Objective C messaging program it's crickets.
- drdaeman 4y ago> So the maid replaces your keyboard instead Well, it's another level of sophistication, requiring some more investment? Replacing a bootloader or a kernel (or initrd) and disabling Secure Boot is easy for just about anyone with 5-10 minutes access to a machine. A modified keyboard is less so.
- userbinator 4y agoLess than a minute is enough to install a hardware inline keylogger. IMHO if you're truly worthy enough to be targeted by such attacks, "secure" boot isn't going to stop them.
- deleted 4y ago[deleted]
- smileybarry 4y agoThen you set an administrator password in your BIOS and prevent changes by anyone but you. Some laptops even allow you to use the fingerprint reader for this. (Had a ThinkPad that did this)