"Stuff like UEFI also gives governments stricter controls over people (like dissidents)."There is a newly-discovered issue involving systemd
and EFI/UEFI. This has shown up in several prominent online forums and also in bug reports for almost a week (or longer). I had mentioned it online for a while, but only earlier today did I decide I have enough of a confirmation regarding this severe problem. It is now mentioned in news sites, too [1,2,3], so I wanted to very quickly remark on it (due to lack of time), noting that here again we have an example of remote bricking by means of UEFI -- a subject that the NSA previously warned about (accusing China, warning that it had attempted to do something similar).
Don't accept UEFI. Like DRM, TPM and many other malicious 'features', it is intended to give corporations control over the users, rather than enable the users to control their computers better. Stuff like UEFI also gives governments stricter controls over people (like dissidents). ⬆
Related/contextual items from the news:
Running rm -rf / on any UEFI Linux distribution can potentially perma-brick your system.
As a public service announcement, recursively removing all of your files from / is no longer recommended. On UEFI distributions by default where EFI variables are accessible via /sys, this can now mean trashing your UEFI implementation.
It’s fairly stupid to run such a command, but usually not destructive to anything but the Linux installation. However, as it turns out, on MSI laptops it’s possible to completely wipe the EFI boot partition from inside Linux.
Running rm -rf / on any UEFI Linux distro can potentially perma-brick your system, Windows PCs also vulnerable