Post BAZHHzYIr7VFf7TVWS by niconiconi@mk.absturztau.be
 (DIR) More posts by niconiconi@mk.absturztau.be
 (DIR) Post #BAZHHzYIr7VFf7TVWS by niconiconi@mk.absturztau.be
       0 likes, 0 repeats
       
       @datenwolf@chaos.social I bet nobody is interested in fixing the problem, because it's only an issue if you manage /etc/resolv.conf by hand which is rarely done these days. If you use systemd with both -networkd and -resolved activated, which is the standard these days, /etc/resolv.conf is automatically generated by systemd, and DNS is also provided by systemd. The auto-generated configuration files would override the default behavior (because systemd's option UseDomains= is an empty string by default exactly because of this vulnerability), meaning that most deployments are not affected.  pass the developers of the Linux networking tools a copy of the *BSD manual I won't be surprised if the "hostname" does this because it's a kernel space limitation. It probably is."not apt for an age of 'servers are cattle not pets'"I bet the glibc code was last touched in the early 2000s, and nobody really cared about it anymore because of "servers are cattle not pets", as it affects manual workflows more than automatic workflows with systemd.