Skip to Content [alt-c]


In reply to How to Crash Systemd in One Tweet

Anonymous on 2017-06-30 at 04:52:

I'm late to the party on this, and doubt anyone will see my comment, but after reading "...Been saying it for a while...systemd is ready made for a rootkit." I felt I had to.

There are already rootkits in the wild. Systemd is a nasty piece of work. I'm back to slackware now and it took eons to get a clean install. My whole system was junked.

I can't go into detail because it would take a dissertation to explain everything and as a linux user of more than 20 years still don't fully understand, but basically it involves the use of systemd, containers - and actually uses portions of selinux against you. You think you su in bash but you're not root. Real root is 'above' root. All formatting say /dev/sda1 does is format the container equivalent of what's called /dev/sda1 so it's a nightmare to break out of. Shit is copied back on reinstall of other systems.

Sorry for incorrect terms (English second language).


Post a Reply

Your comment will be public. To contact me privately, email me. Please keep your comment polite, on-topic, and comprehensible. Your comment may be held for moderation before being published.

(Optional; will be published)

(Optional; will not be published)

(Optional; will be published)

  • Blank lines separate paragraphs.
  • Lines starting with > are indented as block quotes.
  • Lines starting with two spaces are reproduced verbatim (good for code).
  • Text surrounded by *asterisks* is italicized.
  • Text surrounded by `back ticks` is monospaced.
  • URLs are turned into links.
  • Use the Preview button to check your formatting.