News for hackers. Stuff that matters.

A comment on Systemd as tragedy. Parent comment

Re:Systemd as tragedy by chris_wot on Tuesday January 29, 2019 @04:26AM (#19024994)
Actually, that was nothing to do with systemd. That was definitely a UEFI implementation issue. And systemd didn't delete anything, the user did - they ran:

  rm -rf --no-preserve-root /
https://lwn.net/Articles/674940/
[ Parent | on HN ]
Re:Systemd as tragedy by majewsky on Tuesday January 29, 2019 @05:18AM (#19025218)
The bug was in the kernel (it should not have allowed userspace to write arbitrary UEFI variables), but AFAIR it was exposed by systemd because it eagerly mounted the UEFI variable filesystem provided by the kernel into /sys/something/efivars.
[ Parent | on HN ]
Re:Systemd as tragedy by chris_wot on Tuesday January 29, 2019 @06:13AM (#19025430)
Indeed, but again that was a firmware issue. systemd didn't delete the variables. And systemd was setting EFI variables, so consequently it needed it to be mounted as read/write.

The configuration files should have set that to read only after boot.

The kernel patch where this was fixed can be found here:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...

[ Parent | on HN ]