Re: [Bug 32906] Re: sudo shouldn’t ABSOL UTELY NEED to look up the host it’s running on
I don't understand this. I can see the proper listing in the hostfile and I still have the problem. But I didn't edit it in recovery mode. Why must I do that and how do I do the recovery mode boot? Scott -Original Message- From: Pasi <[EMAIL PROTECTED]> Reply-To: Bug 32906 <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: [Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on Date: Sat, 26 Apr 2008 17:18:29 - I encountered this same problem after upgrading from gutsy to hardy. After trying to resolve connection problems which were messed up after the upgrade the sudo stopped working. It happened when I disabled my wireless and lan connection from kde network management tools. Booting in recovery mode and adding the host name back did fix the problem. I find this very serious problem since ubuntu relies so heavily on sudo (the lack of root account) and if that command fails there is no way to do anything. sudo should not depend on network configurations. It sounds very very dangerous! -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 32906] Re: sudo shouldn’t ABSOL UTELY NEED to look up the host it’s running on
Hi, agent 8131 [2008-04-25 22:40 -]: > Furthermore, Martin Pitt has also stated that he does not consider this > to be a bug No, that's wrong. I do consider it a bug. I just have trouble with reproducing it. It's still assigned to me and open. -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 32906] Re: sudo shouldn’t ABSOL UTELY NEED to look up the host it’s running on
Dorin Lazăr [2008-03-20 7:44 -]: > Going back to this bug: this happened to me when I upgraded to one > of the alphas of ubuntu. However, instead of seeing only the problem > in the network settings, I want to point the design mistake in sudo. > What would've happened if my hostname was actually other machine's? > does that mean that I could've sudo stuff on other machine even if > the local policy disallowed it? If you configure your local sudoers in a way that you have privileges on a machine 'foo', and no privs on a machine 'bar', and you change your hostname from 'bar' to 'foo', then yes, you'll get privileges. That's exactly what host-based sudo configuration is meant to do. (This is not the default, but it's convenient for sharing sudo configuration amongst multiple machines). -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 32906] Re: sudo shouldn’t ABSOL UTELY NEED to look up the host it’s running on
asmoore82 [2008-03-15 19:17 -]: > $ sudo -k > # sed -i "s/pickles/foobar/g" /etc/hosts > $ sudo true > sudo: unable to resolve host pickles In your comment further down you said that this broke. Why do you think so? The -k actually worked, since in the next sudo command you had to enter your password again: > # hostname foobar > $ sudo -k > $ sudo true > [sudo] password for asmoore: I advise you to test sudo with something that gives visual feedback about whether it worked or not (which is not the case with 'true' and -k). I recommend "sudo id" and verifying that you get output adequate for root (user id 0). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) My 5 today: #198129 (tzdata), #189854 (gst-pulse), #200739 (bind9), #200785 (xserver-xorg-video-nv), #189995 (langpack-locales, belocs- locales-bin) Do 5 a day - every day! https://wiki.ubuntu.com/5-A-Day -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 32906] Re: sudo shouldn’t ABSOL UTELY NEED to look up the host it’s running on
kmon [2008-03-13 20:49 -]: > Changing > Defaults !lecture,tty_tickets,!fqdn > to > Defaults env_reset > > and now it works as martin says Aah - so it only happens if fqdn is switched off? Interesting, since that should actually be the case when sudo does *not* use gethostbyname and thus not care about broken hostnames. I'll give this a try, thanks for the hint. -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://bugs.launchpad.net/bugs/32906 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
