SoylentNews is people
SoylentNews
Whether you're running systemd happily or begrudgingly, it's best if you disable systemd-resolved as your DNS resolver for the time being. Reported today at seclists is a new DNS cache poisoning bug in systemd-resolved.
At its simplest, an attacker triggers a query to a domain he controls via SMTP or SSH-login. Upon receipt of the question, he can just add any answer he wants to have cached to the legit answer he provides for the query, e.g. providing two answer RR's: One for the question asked and one for a question that has never been asked - even if the DNS server is not authoritative for this domain.
Systemd-resolved accepts both answers and caches them. There are no reports as to the affected versions or how widespread the problem may be. Comments over at Hacker News suggests that it might not be widespread, most users would still be running the backported 208-stable while the DNS resolver was committed in 213 and considered fairly complete in 216, but that is if they enabled systemd-resolved in /etc/nsswitch.config.
(Score: 2) by LoRdTAW on Thursday November 13 2014, @02:41PM
I fully realize your post is humorous but it demonstrates peoples ignorance of just what systemd actually is. )See my post above : http://soylentnews.org/comments.pl?sid=4834&cid=115518 [soylentnews.org]
Systemd is much more than a simple init system and PID1. It is a bad idea, copies bad design (see the wikipedia link in my other post) and adds nothing of value.