Most people, including the authors of systemd would be very surprised if there were no problems with systemd. Here's a couple of fun problems from years past.

Most people, including the authors of systemd would be very surprised if there were no problems with systemd. Here's a couple of fun problems from years past. Docs say NoNewPrivileges as yes "prohibits UID changes of any kind", but that's not exactly true. It's spammed so much debug info the system fails to boot. "systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files." "The rm_rf_children function in util.c in the systemd-logind login manager in systemd before 44, when logging out, allows local users to delete arbitrary files via a symlink attack on unspecified files, related to "particular records related with user session." It's complex software running on many different kernels, and many different distributions, doing many different things with lots of code written in C. There were over 80 people mentioned as contributing to the last release. Of course there are going to be problems!