-
Systemd-init has a larger attack surface compared to runit, openrc, or sysVinit.
-
Systemd-logind relies on systemd, so we need to adapt it for non-systemD distributions to ensure compatibility with certain applications like GNOME.
-
Udev also depends on systemd.
-
SystemD is specific to Linux, which makes porting software to *BSD even more challenging. It’s uncertain what the future holds, and there may be circumstances where Linux becomes unusable for you (e.g., compatibility issues with your laptop). Having a good alternative that doesn’t require relearning everything is generally beneficial.
-
SystemD-based distributions often come with more than just “systemd-init.” They include additional components like logind, resolved, networkd, systemd-timers, etc. However, many people still prefer using the alternatives they were accustomed to before systemd became popular, such as dhcpcd and cron. Consequently, having both sets of tools installed can increase the attack surface.
So what? Linux Kernel has an even larger attack surface, the size of the attack surface is a moot point without examples of attacks being made
Yes, systemd modules depend on systemd, that’s like complaining that a GUI application depends on X.
It doesn’t, that’s ridiculous, several distros don’t use systemd and still have udev
If your laptop doesn’t run Linux it will not run BSD since BSD has less hardware compatibility than Linux. Also BSD is a different system, you’ll need to relearn a lot of things, how to enable services is just one of them, and a pretty small one at that. And Finally there are forks of systemd that work on BSD, the reason it’s not used there is not technical.
Again, more attack surface does not mean anything, to add to that example most people use the precompiled kernel that comes with their distro instead of compiling a leaner one to diminish attack surface, because that’s irrelevant. You could have said let’s your system bloated which would be a somewhat valid point, the answer being if the person cared they would uninstall one of the alternatives, but you chose the most insignificant aspect of this, if there’s a vulnerability in your computer it’s 99.99999% coming from whatever you exposed in that computer, e.g. SSH, Nextcloud, etc, chances of an attack coming through systemd are so ridiculously small it’s not even worth mentioning, and if ever someone discovers an escalation privilege or something similar on systemd the fact that everyone uses it will make the fix available in 24h on most major distros.
There are reasons to hate on systemd, but you didn’t provided a single valid one.
SystemD is not modular. Logind is just an executable that depends on systemD libs. Red Hat could design it to be init-agnostic(similar to elogind). But they didn’t. Any assumptions, why?
Yes module is not the correct word, but that’s nitpicking, the concept is still the same, it’s a binary that depends on systemd, that’s a developer choice, same as using GTK or Qt, there are up and downsides to choose what your program depends on, the developers of systemd-logind decided to depend on systemd knowing the downsides, and distros decide to use it also knowing of them. As for your question possibly the answer is that the added difficulties of making it system agnostic did not compensated for the low user base, same reason most games don’t have a native binary.
Looks like Red Hat makes everything they can systemd-dependent. Including Gnome.
Void uses eudev. Alpine uses eudev. Gentoos uses udev with patches. What non-systemd distros use vanilla udev?
Ah, so with udev you meant systemd-udev, in that case the answer is the same as systemd-login, complaining that a systemd module doesn’t work outside of systemd is ridiculous.
See the answer on your logind statement.
The thing is that it can work. Which shown by eudev. Looks like it’s important for Red Hat to make everyone dependent on SystemD suit.
Most people also don’t use selinux or apparmor, compile the kernel with -ftrivial-auto-var-init=zero and verify downloaded files using pgp signatures. But it doesn’t mean these things are irrelevant. Even your phone has selinux=enforced option set. Why do you think your pc is not worth it?
You went on a tangent, my point is that larger attack surface does not necessarily equate to more risk. As an example my kernel has controller support even though I have never plugged a controller to it, that grants it a larger attack surface, but does not make it less secure in any significant sense of the word. Therefore just claiming larger attack surface is not a valid criticism on it’s own unless you can provide examples of actual security flaws.
There is an example: https://www.agwa.name/blog/post/how_to_crash_systemd_in_one_tweet
If a bug that was fixed over 7 years ago is your best example of security failure in systemd I think that’s proof enough that it’s safe.
Compare it to vulnerabilities found in SysVinit, which was as common as systemd-init is now. There were no similar bugs, that would allow crashing an entire system just by executing a single command.
There might not have been those kinds of bugs in sysvinit itself but the shitty quality init scripts it encouraged people to write certainly had thousands of security issues.
Misconfiguration is possible in any software. It’s not specific to sysvinit or systemd-init. Selinux was created to solve this.