> The grandparent comment was about how the issue was actually systemd. It's not my view that "the issue was actually systemd". The issue was a complex, sophis

> The grandparent comment was about how the issue was actually systemd. It's not my view that "the issue was actually systemd". The issue was a complex, sophisticated attack by someone taking a long view. But the attacker injected his code into the system by manipulating part of systemd into loading a fairly obscure compression library that he had hacked. Systemd is of course more-or-less omnipresent these days. Why does an init system need to load libraries at all? Well, it doesn't, unless it has arrogated to itself much more functionality than PID1 should ever have.