<story><title>Systemd mounted efivarfs read-write, allowing motherboard bricking via &apos;rm&apos;</title><url>https://github.com/systemd/systemd/issues/2402</url></story><parent_chain><item><author>mmastrac</author><text>These threads are never productive. Running rm -rf &amp;#x2F; is going to offer multiple interesting ways to make your life miserable, eg: a mounted FUSE filesystem, an NFS folder pointed somewhere important, Samba mounts from your network automatically connected from your desktop, etc. I wouldn&amp;#x27;t be surprised if you could nuke firmware off a device by deleting the appropriate file in &amp;#x2F;sys&amp;#x2F;.&lt;p&gt;Systemd hate is en vogue these days so they are an easy and common target. Why no invective towards the kernel that actually implements EFI-as-a-filesystem?</text></item></parent_chain><comment><author>mikeash</author><text>Sometimes people run rm -rf &amp;#x2F; just for fun before reformatting a system, just to see what happens. Given that its purpose in life is to delete files, it stands to reason that running this command on a system which contains no important data is OK. A &lt;i&gt;default&lt;/i&gt; configuration which makes this command &lt;i&gt;destroy hardware&lt;/i&gt; is not reasonable.</text></comment>
<story><title>Systemd mounted efivarfs read-write, allowing motherboard bricking via &apos;rm&apos;</title><url>https://github.com/systemd/systemd/issues/2402</url></story><parent_chain><item><author>mmastrac</author><text>These threads are never productive. Running rm -rf &amp;#x2F; is going to offer multiple interesting ways to make your life miserable, eg: a mounted FUSE filesystem, an NFS folder pointed somewhere important, Samba mounts from your network automatically connected from your desktop, etc. I wouldn&amp;#x27;t be surprised if you could nuke firmware off a device by deleting the appropriate file in &amp;#x2F;sys&amp;#x2F;.&lt;p&gt;Systemd hate is en vogue these days so they are an easy and common target. Why no invective towards the kernel that actually implements EFI-as-a-filesystem?</text></item></parent_chain><comment><author>cmhamill</author><text>The issue here is actually &lt;i&gt;bricking&lt;/i&gt; the device. It&amp;#x27;s not your standard &amp;quot;do we let people hang themselves or limit the user&amp;#x27;s capabilities&amp;quot; debate.&lt;p&gt;A filesystem is a perfectly reasonable way to implement access to the EFI vars.</text></comment>