Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin...
by loeg on Monday February 22, 2016 @02:27PM
(#11153532)
The firmware author(s) should not brick their hardware when EFI variables are deleted. That is an invalid behavior.
[ Parent
| on HN ]
Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin...
by kbenson on Monday February 22, 2016 @02:33PM
(#11153582)
Agreed, but that's almost a non-sequitur. The systemd developers are not the firmware developers. Additionally, while preferably we would have better firmware that couldn't be bricked in this way, we live in a world where this is often not the case, so the problem does need to be mitigated in some manner.
Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin...
by snuxoll on Monday February 22, 2016 @08:00PM
(#11155653)
Bingo! While preventing a user from accidentally hosing their system due to a bad firmware implementation this still does nothing to address potential malware, it's good to have a patch that helps but I think any blame directed at systemd or the kernel devs really needs to be redirected at poor firmware engineering efforts. Mounting efivars as ro is a bandaid, this patch is a bandaid - the real damage is yet to be done!
Re:Linux 4.5-rc5: efivarfs fixed to avoid “rm -rf /” brickin...
by pyre on Monday February 22, 2016 @02:55PM
(#11153745)
The amount of software that requires write access to EFI variables (as root) is pretty small, so leaving it open all of the time in an environment where the firmware writer could have bugs that cause this seems like it's not necessarily the best course of action.