Post #1103737

@mia@shrimptest.0x0.st It's not even security, because there is no privilege boundary breach here: everything is running as root, it's all collaborative. The whole reason for this entire mess is that systemd's supervisor is monolithic (ooooh, the M-word - it actually applies here) and uses one single socket to receive notifications from all its units. So, it needs to authenticate the clients when they send their notification message. It could pass a pipe to the units instead, or, as @navi@social.vlhl.dev suggests, one end of a socketpair if they need two-way communication and fd-passing. That would work perfectly. But it's systemd, so it uses a suboptimal solution and adds hacks upon hacks in order to make it work. Yes, this is madness. But we are not all putting up with it. It's just that, unfortunately, systemd has wildly expanded thanks to an aggressive deployment policy backed up by Red Hat and such. We are trying to reconquer ground, but it goes slowly because we're lacking manpower. (Edit: clarity and accuracy)