Systemd Talks Up Automatic Boot Assessment in Light of the CrowdStrike Outage
phoronix.com
phoronix.com
However good or bad the intentions and ideas here might be, the project has demonstrated many times over that it is not capable of reliably filling the roles to which it aspires. I'm not interested in extending its reach even further.
In short, no thanks.
Ubuntu Core (eg. for the upcoming immutable desktop) also supports this kind of thing fully automatically.
So it's not just systemd and the alternatives are widely deployed already.
But anyway as others point out it won't mitigate risk on a system that injects bad code from outside of the boot process.
It's probably the worse thing to do to give the key to the boot kingdom to systemd, doing random things to your configuration when it feels so...
systemd.io/AUTOMATIC_BOOT_ASSESSMENT/ : https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/
From https://news.ycombinator.com/item?id=29995566 :
> Which distro has the best out-of-the-box output for:?
systemd-analyze security
> Is there a tool like `audit2allow` for systemd units?And also automatic variance in boot sequences with timeouts.
Where does it explain that a systemd service unit is always failing at boot?
> For EFI you could probably set BootNext to something else early on, in combination with some restarting watchdog. GRUB can store state between boots https://www.gnu.org/software/grub/manual/grub/html_node/Envi... and has "default" and "fallback" vars.
Any assessment systemd could have done would see failure to boot, and would either try to roll back to a kernel with an old agent module version, which would probably do the same thing, or go back to a kernel without the Crowd Strike Module at all if available.
Computers aren't magic. They don't know things. They can't bisect their own configuration or intuit what subcomponent caused what behavior. That's your job.
But if you click in, what's being tried monitored & reverted is boot loader entries. From the second sentence in https://systemd.io/AUTOMATIC_BOOT_ASSESSMENT/ :
> The Boot Loader Specification describes how to annotate boot loader entries with a counter that specifies how many attempts should be made to boot it.
Which include kernel parameters. Which include the root. As a btrfs user, my system could take a snapshot before applying an update, & set that as the fall through loader entry, so that if boot fails I go back to that previous state.
I'm again finding myself 100% on Team Lennart here. Again this seems like the obvious right & true path, & like we obviously should be doing this.