In #940260 I wrote (in reverse order): > 3. Perhaps the maintainer scripts should detect a flawed-netcfg-corrupted > /e/n/i and either notify the admin or give her the opportunity > (via debconf?) to repair the corrupted file.
Steve Langasek's change in 1.63ubuntu9 implements the most important aspect of this, namely, not to accept garbage as a valid IP address for the purpose of deciding whether or not to append the original file. A fix-the-bogus-dns-nameservers-line wizard would be nice, but if we were going to do that we would simply write a wizard for configuring ifupdown for resolvconf. What would be the correct way to implement such a thing in Ubuntu? > 2. Perhaps resolvconf should check the validity of each nameserver > address string fed to it. Currently it doesn't do so, even though it > does some "normalization" of address strings. The normalized_stdin() function in /sbin/resolvconf should also be enhanced to filter out bogus nameserver addresses. Otherwise those addresses will end up in resolv.conf, which is not what we want. This is a non-negligible issue, I think. > 1. We need to check ifupdown and resolvconf code, thinking about > what will happen when they get fed such dns-nameservers lines. I will do this sometime this week, even though it means reading ifupdown code, which may still be written (yikes) in Literate Programming. ;) -- Thomas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/932275 Title: Bogus or no nameserver information written to /etc/network/interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/932275/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
