[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Aah, I finally found out why I could not reproduce it, and what's wrong. I have local MTAs on all my boxes. If I install a system without one, I can replicate the error. It apparently tries to send a mail to the admin about the error and dies with a SIGPIPE: Program received signal SIGPIPE, Broken pipe. 0x7fcef7181bb0 in write () from /lib/libc.so.6 (gdb) bt #0 0x7fcef7181bb0 in write () from /lib/libc.so.6 #1 0x7fcef7125ce3 in _IO_file_write () from /lib/libc.so.6 #2 0x7fcef7125bc4 in _IO_do_write () from /lib/libc.so.6 #3 0x7fcef7126e20 in _IO_file_close_it () from /lib/libc.so.6 #4 0x7fcef711adfa in fclose () from /lib/libc.so.6 #5 0x00405d36 in send_mail (line=0x62fe60 unable to resolve host foo) at ../logging.c:564 #6 0x00406637 in log_error (flags=9, fmt=0x411d08 unable to resolve host %s) at ../logging.c:432 #7 0x00407cf8 in set_fqdn () at ../sudo.c:1160 #8 0x00408c4d in main (argc=value optimized out, argv=value optimized out, envp=0x7fa46208) at ../sudo.c:608 This looks suspiciously similar to bug 193516. I'll take a stab at this now. ** Summary changed: - sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on + sudo fails if it cannot resolve the local hostname and no MTA is installed ** Tags removed: gutsy2hardy -- sudo fails if it cannot resolve the local hostname and no MTA is installed 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I've had this problem with both a fresh install and an upgrade to Hardy. George Durbridge's and Phosgene's experience matches mine - using the network admin tool, sudo works ok without domain name, but can't sudo with a domain name. Unfortunately, my 'workgroup' uses a domain name! -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I have to say I agree with SteveR in comment 56. The chicken and egg problem here is likely a deal breaker for more than a few remote server administrators. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Changed in: sudo (Ubuntu Hardy) Target: None = ubuntu-8.04.1 -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
This problem occurred for my friend on his laptop when he upgraded from Gusty to Hardy. I first tried going into recovery mode and resetting the hostname, but there was no change. So instead I used the network-admin to change /etc/hosts; I aliased 127.0.0.1 as the hostname and localhost. I'll try reproducing this on my own machine later, and see if I can confirm that network-admin corrupts the hosts file by adding the domain to the end of the host. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I just upgraded from 7.10 to 8.04 with the effect that I could not sudo any more (unable to resolve host name) the problem is that my sysadmin had advised me to remove the line 127.0.1.1 myhostname from /etc/hosts a couple of days before the upgrade. When I put it back in, sudo worked again. mmh, a bit tricky that you cannot sudo because your network settings are wrong, and you cannot change your network settings because you cannot sudo. maybe some more thought is required here, it is too easy to make your system unsteerable... -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
What I have to do to get the sudo to work: 127.0.0.1 localhost #127.0.1.1 Ubuntu-Tower.NTWorkgroup ###commented to see if it will fix sudo### 127.0.1.1 Ubuntu-Tower With the .NTWorkgroup, I can 't use Update Manager, Root terminal etc. etc. I had to use the normal Terminal followed by su to edit the hosts file so I think I am fine now. Just in case anyone cares... -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Having just installed ubuntu 08.04 on a new server, then putting it in a datacenter over an hour away, then copying our master hosts file over and thus loosing the server, I can say that this bug is reason enough for us to drop the whole idea of moving to ubuntu. I think it needs a couple of more years. Obviously not many people use it, or this would not have ever passed through to a release version. The use case for a sys admin setting up network settings is that not all settings are set simultaneously. With no real root account (I was going to set it up soon), a remote server is now completely hosed. This is entirely too fragile to rely upon. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Tags added: gutsy2hardy -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
There is a user in #kubuntu-de at the moment who upgraded from Gutsy to Hardy and did nothing manually to her /etc/hosts or /etc/hostname. After the upgrade sudo stopped working for her. The hostname was still maxi as before the upgrade, but the line in /etc/hosts suddenly said 127.0.0.1 maxl (small L in the end). How that lower case L got there is a mystery. After logging in with recovery mode and changing it to an i, sudo is working again as expected. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Martin Pitt wrote: I just have trouble with reproducing it. Seriously? Here's one way: Boot the 8.04 live CD Open a terminal window Enter the commands sudo id sudo hostname foo sudo id Note how the former sudo id command succeeds but the latter one fails with the error message sudo: can't resolve foo. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
A minor clarification to the above... the exact error message issued by the sudo id command is actually sudo: unable to resolve host foo -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
This is a bug in the network-admin tool. It is not just an upgrade problem, as I encountered it on a fresh install of Hardy. The tool saves a hostname to /etc/hosts in the form host.domain, even if you only enter host. So if you provide for one IP the aliases host and host.domain, it saves host.domain twice, and does not save plain host at all. When sudo looks up host, there is no such entry. You can get around the bug by deleting the domain from the General tab in the network-admin tool, before you use it to enter the hostname for localhost in /etc/hosts. If you restore the domain name later, however, the network-admin tool will corrupt the entries in /etc/hosts, replacing host with host.domain. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I think this bug is marked as In progress and Martin Pitt is assigned to it and from reading the comments (have any of you actually read the comments?), he said in comment #1: I agree that sudo doesn't need to look up the hostname IF the relevant host part in sudoers is ALL anyway. Any comment after that has been pointless, since comment #1 is all this bug is about. If you have any other issue (something breaks your hostname, you don't like sudo's design, etc.), please, open a new bug report or a wiki page or a spec. This is not a discussion forum. This bug is known, this bug is acknowledged, it only remains to give a patch. So if you don't have a patch, you are not helping. On the contrary, you are flooding people's inbox and making them to lose interest in this bug. If you want to help, grab the source code of sudo and figure out how to avoid calling gethostbyname() when /etc/sudoers does not contain any hostname to resolve. As far as I know, sudo is not maintained by Canonical, so bringing the issue to the original developers may also help to solve this bug (perhaps it is already solved in a recent version). http://www.gratisoft.us/sudo/ Thanks. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Please refrain from discouraging people to contribute. People are trying to help by sharing their experiences in hopes that the additional information will be useful to resolving this bug. Furthermore, Martin Pitt has also stated that he does not consider this to be a bug and that does require discussion from those of us who feel that it is a bug. He also mentions (in his first post) that not having an entry for the local machine hostname in /etc/hosts will cause trouble. This is incorrect and needs to be pointed out. The only program that seems to have trouble without such an entry is sudo which is one reason why I think this should be fixed in sudo. However, this is also a bug with multiple potential solutions. These should be considered in deciding an optimal solution. Finally, if anyone does not want to receive mail about this bug by all means unsubscribe yourself. Now, I wanted to address Martin Pitt's concern about reproducing this bug. I wonder if factors such as having a dns caching server might be related to this not being reproducible. However, here are my results from a virtual machine (with no copy and paste so bear with me) running up to date Ubuntu 8.04. /etc/hosts contains: 127.0.1.1 hardy64server /etc/sudoers is the default: Defaults env_reset root ALL=(ALL) ALL %admin ALL=(ALL) ALL $ sudo id [sudo] password for agent: uid=0(root) gid=0(root) groups=0(root) $ sudo nano /etc/hosts comment out hostname line $ sudo -k sudo: unable to resolve host hardy64server $ sudo id sudo: unable to resolve host hardy64server $ su $ nano /etc/hosts restore hostname line $ exit $ sudo id [sudo] password for agent: uid=0(root) gid=0(root) groups=0(root) -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Let's please step back a bit. If we look at things from sudo's point of view, maybe this is just expected behavior and not a bug. But, if you look at it from the Ubuntu project's point of view, this is a major problem. There is simply no way on any kind of robust system _I_ want to be involved with, that messing up a simple configuration file like /etc/hosts can destroy my ability to log in with administration privileges, to _FIX_ the messed up file [*]. The idea that mistyping a host name or (as in my situation) having NetworkManager incorrectly modify /etc/hosts, should mean that I have to reboot with a rescue CD, mount the partition by hand, and edit this file. I hope we can agree on this. So the problem becomes how to resolve this. One simple idea is for sudo to defer the hostname lookup until it's absolutely required. On a standard Ubuntu /etc/sudoers file, it actually is NEVER required because there are no host-based restrictions in the file. So, we never need to know the hostname we're currently logged into. This may not be a solution that works for everyone but it will work for the vast majority of people, who do NOT share /etc/sudoers files and who do NOT have host- specific rules there. [*] I realize that /etc/sudoers is another such file, but hopefully it's pretty obvious that if you mess up /etc/sudoers your ability to use sudo will be adversely affected... not so /etc/hosts and/or /etc/hostname. Also, there is a separate command to modify /etc/sudoers (visudo) which validates the /etc/sudoers file for basic correctness after you've finished editing it... again not so /etc/hosts and/or /etc/hostname. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Here's a list of over 20 threads so far on ubuntuforums with posts describing problems caused by this bug: http://hightechsorcery.com/2008/04/partial-list-ubuntuforums-threads- related-sudo-unable-resolve-host-bug -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I upgraded to 8.04 today and am having the same problem. Whenever I use sudo I get the error: sudo: unable to resolve host hostname -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I upgraded 7.10 to 8.04 today (23-04-2008). sudo was borked due to unable to resolve host. I removed 127.0.1.1 montreal.ubuntu.com ubuntu from /etc/hosts file in recovery mode. BAM! It worked perfectly. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I confirm this bug in a dist-upgrade from Kubuntu Gutsy to Hardy (18/04/2008), without touching any config file. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I ran into this recently. My use case was copying virtual machines and then changing the hostname by editing the /etc/hostname and running hostname -F. I was surprised to see sudo stop working following this and requiring me to boot into single user mode to fix. My surprise was because there was no reason for sudo to be doing a hostname lookup. In fact I'm not convinced that sudo should ever be doing a hostname lookup. The only case where one could argue the necessity is if one uses an IP address as a Host_Alias. I've never done that, and don't see much sense in it. But certainly if an IP address is not specified as a Host_Alias there's no reason to be doing a lookup. This raises my curiosity as to exactly what sudo is doing and whether it can be exploited. Not being able to resolve the local hostname is a broken and unsupportable state for any *X system. I beg to differ. No Ubuntu system thus far has required the local hostname to be /etc/hosts. None of the desktop systems I am using running Gutsy have such an entry. Thus, if this is not fixed, assuming that Hardy is not going to modify the /etc/hosts file, this bug has the potential to break a large number of systems when they attempt to upgrade. I'd be very careful and get this resolved correctly. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I fixed my error sudo: unable to resolve host lian-ubuntu-beta by making entries in System-Administration-Network such that afterward the files /etc/hostname and /etc/hosts read: $ cat /etc/hostname lian-ubuntu-beta [EMAIL PROTECTED]:~$ cat /etc/hosts 127.0.0.1 localhost lian-ubuntu-beta 127.0.1.1 lian-ubuntu-beta 192.168.1.103 lian3.foxgulch.net lian3 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Specifically System-Administration-Networking Unlock Then Authenticate then In the Hosts Tab highlight the 127.0.0.1 localhost line click properties make it read IP address: 127.0.0.1 Aliases : localhost lian-ubuntu-beta In the General Tab Hostname: lian-ubuntu-beta Domain Name: (nothing or blank) -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
This is a link to the Ubuntu forums that shows how to do what LarryJ states above. http://ph.ubuntuforums.com/showthread.php?p=4480244 Quick and very easy fix. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
The sudo+hostname bug/inconvenience happened to me. I hosed my hosts file when upgrading from 7.04 to 8.04. Sudo didn't want to do anything, but gksudo worked fine. The network-dependent sudo failed, but the X11-dependent gksudo was OK. Redundancy saves the 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I was getting the same problem, sudo: unable to resolve host ABIT, where ABIT is my HOST NAME. I fixed this problem by going to System==Administration==Network, under the General tab, I put my Domain Name as home.local , -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
@asmoore I am not confused at all. I actually am certain that raising privileges on the local machine should not require networking bits at all. There is no real reason why that should be done. No real dependency of the network, unlike the X system that is actually meant and thought for networking. That, however, doesn't mean that other applications that use X are broken. If gnome-terminal starts in 60 seconds and xclock in .001 seconds, and you blame it on X, you might very well have a diagnosis problem. 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? And once again, my point of view: raising privileges on the LOCAL machine should NOT require networking bits. NEVER. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Convenient, no doubt - but I see it as a positive side effect of a defective behaviour rather than something intentional and positive. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I actually am certain that raising privileges on the local machine should not require networking bits at all. There is no real reason why that should be done. No real dependency of the network, unlike the X system that is actually meant and thought for networking. In your own terms: The `sudo` system _IS_ meant and thought for networking! And even so, resolving the _LOCAL_ hostname is not networking bits. And once again, my point of view: raising privileges on the LOCAL machine should NOT require networking bits. NEVER. You are willfully ignorant of and blurring the line between _LOCAL_ hostname and networking bits. The _LOCAL_ hostname _IS_ mandatory and does not constitute networking bits. Of course it is no bug in the sense that it breaks any specified contract, but ubuntu does not have a password for root and sudo is the only way to repair a wrong /etc/hosts. Precisely, I say that this non- bug can be closed/resolved/cancelled! Discussion of repairing the _local_ hostname configuration is already here: https://bugs.launchpad.net/ubuntu/+source/rescue/+bug/19553 -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Sir, I seriously think that sudo is meant to raise/change privileges of the current user, and this has nothing to do with the network. The manual page makes this short description: sudo, sudoedit - execute a command as another user. But I am certain that you can explain me who says that the local hostname is mandatory, and in what circumstances. My strong belief, as an expert computer user, is that if no host was specified in the command line or sudoers file, there should be no resolving whatsoever. Please fix bugs, don't bloat the software! I don't want my system to become more fragile than Windows 95. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
@Dorin Perhaps sudo should try to use the name from /etc/hostname when gethostbyname fails? It looks quite simple to do that, and assume that you'll have there 127:0.0.1 (in both IPv4 and v6)?!?!?! You seem to be confused. That's _exactly_ what `sudo` is doing: it's using the known _local_ hostname which would've been set in /etc/hostname. It has to resolve this _local_ hostname and does so with the _local_ /etc/hosts file. gnome-terminal is simply broken if it needs to resolve any kind of hostname during startup. you are aware that the X Window System is a client-server setup over the loopback interface aren't you?!? Apps should _always_ be able to resolve the _local_ hostname and some have come to rely on this fact. @everyone *_There is no bug here_* The original bug reporter in the _blog_ overwrote his /etc/hosts file and in doing so broke his _local_ host configuration. `sudo` errors were merely the first symptom he noticed of his newly broken system. *_To prove that something is wrong with sudo_* you would need to show a situation where `sudo` does _not_ work but the following does: ~$ grep `hostname` /etc/hosts ***Revised Proof: Same machine, 2 terminals; root breaks and fixes the system; asmoore tests sudo: - [EMAIL PROTECTED]:~$ grep `hostname` /etc/hosts 127.0.1.1 pickles [EMAIL PROTECTED]:~$ sudo id [sudo] password for asmoore: uid=0(root) gid=0(root) groups=0(root) [EMAIL PROTECTED]:~$ sudo -k [EMAIL PROTECTED]:~# sed -i s/pickles/foobar/g /etc/hosts [EMAIL PROTECTED]:~$ grep `hostname` /etc/hosts [EMAIL PROTECTED]:~$ sudo id sudo: unable to resolve host pickles [EMAIL PROTECTED]:~$ sudo -k sudo: unable to resolve host pickles [EMAIL PROTECTED]:~# hostname foobar [EMAIL PROTECTED]:~$ grep `hostname` /etc/hosts 127.0.1.1 foobar [EMAIL PROTECTED]:~$ sudo id [sudo] password for asmoore: uid=0(root) gid=0(root) groups=0(root) [EMAIL PROTECTED]:~$ sudo -k [EMAIL PROTECTED]:~# hostname `cat /etc/hostname` [EMAIL PROTECTED]:~# sed -i s/foobar/pickles/g /etc/hosts [EMAIL PROTECTED]:~$ grep `hostname` /etc/hosts 127.0.1.1 pickles [EMAIL PROTECTED]:~$ sudo id [sudo] password for asmoore: uid=0(root) gid=0(root) groups=0(root) [EMAIL PROTECTED]:~$ sudo -k - Adam sM -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Of course it is no bug in the sense that it breaks any specified contract, but ubuntu does not have a password for root and sudo is the only way to repair a wrong /etc/hosts. On systems with root passwords this would be a non-issue. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Just because applications like gnome-terminal or mc are broken doesn't mean that on your local box there should definitely be no resolving done. Or if there is some kind of resolving done, resolve 127.0.0.1 or localhost (just to be not so IP-minded) But I see NO reason for sudo to make any DNS resolving unless necessary. And it's not necessary for any kind of local work. There is no sane use-case for sudo to resolve the localhost unless enforced by policy, but even then the policy is wrong. Why is it wrong? You're on your local machine, you definitely need no network working, there definitely shouldn't be ANY networking done, and any networking done during local privileges raising should be seen as a security threat. mc is wrong to resolve hostnames during startup because, well, it doesn't start with a network view. gnome-terminal is simply broken if it needs to resolve any kind of hostname during startup. Just because it's a general solution doesn't mean it's a good solution. What's local should stay local, and I might suspect a security flaw in sudo if it does DNS resolving for localhost :) -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Changed in: sudo (Ubuntu Hardy) Status: Incomplete = In Progress -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
@Martin $ sudo true sudo: unable to resolve host pickles ^^ This is where sudo was broken. I can re-run the test using `sudo id` when I get back to my Hardy box; But, again, I feel there is no bug here: Not being able to resolve the local hostname is a broken and unsupportable state for any *X system. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
@asmoore82 But, again, I feel there is no bug here: Maybe you are right if you have a new installation of hardy. But consider there is a different behavior in hardy compared to previous releases (e.g. gutsy) where a different hostname in /etc/hostname and /etc/hosts is accepted. If this is kept there is an gutsy-hardy update problem. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
sudo does not work by default if your network card is only partially supported, as opposed to logging in with root. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
But consider there is a different behavior in hardy compared to previous releases (e.g. gutsy) where a different hostname in /etc/hostname and /etc/hosts is accepted accepted by `sudo` or accepted in general ?? I can get away with that on my Gutsy box, but it _is_ a misconfiguration and causes certain programs(such as `gnome-terminal`) to take much longer to 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I can reproduce the bug in Hardy: barcc:~$ sudo grep -v '^#' /etc/sudoers | grep -v '^$' Defaults!lecture,tty_tickets,!fqdn,timestamp_timeout = 15 rootALL=(ALL) ALL %admin ALL=(ALL) ALL root:~# hostname foobar barcc:~$ sudo id sudo: unable to resolve host foobar It warns and fails But if i start aptitude -Actions-Become root, i get: barcc:~$ aptitude sudo: unable to resolve host foobar [sudo] password for barcc: And now in aptitude i am root. Now i changed sudoers: barcc:~$ sudo grep -v '^#' /etc/sudoers | grep -v '^$' Defaults env_reset rootALL=(ALL) ALL %admin ALL=(ALL) ALL But i get the same results barcc:~$ sudo id sudo: unable to resolve host foobar -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I can confirm similar behavior on Hardy Alpha6 to what's shown above, _but_ I say that there is no bug here. The behavior stems from the fact that the hostname is preset in 3 locations: 1. /etc/hosts 2. /etc/hostname which, in turn, sets the precedent for 3. The kernel itself and/or the Environment If you change the hostname from within the `network-admin` tool, you have no issues with `sudo` _and_ the tool warns you that your system will be in an inconsistent state until the next reboot. Steps to confirm the lack of a bug: I, too, use 2 terminals, 1 in a `sudo -s` session as a failsafe and a second to test for breakage of `sudo` in general. The commands are posted in the order I execute them and you can use the leading '$' or '#' to distinguish between the 2 terminals: - # hostname pickles $ sudo true [sudo] password for asmoore: $ sudo -k # sed -i s/pickles/foobar/g /etc/hosts $ sudo true sudo: unable to resolve host pickles # hostname foobar $ sudo -k $ sudo true [sudo] password for asmoore: - Observe that `sudo` went from working, to broken, to working again as I restored the system to a semi-consistent state by having `hostname` and /etc/hosts agree. Note that, had I rebooted right after, `sudo` and many other things would've been broken again because /etc/hosts and /etc/hostname do _not_ agree; this, too, is _not_ a bug. The original bug reporter needs to understand that: 1. His system is broken simply because he broke it. 2. Freedom means free to do anything, even if it is destructive. 3. A blog post does not a bug report make. IMHO, this bug report is akin to `sudo rm -rf` hosed my system! Adam sM, ubuntuforums.org member, my first launchpad.net posting. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Sorry for the double-post, but in a more direct response to the YELLING in the topic: If sudo behaved differently, it would become vulnerable to some sort of `HOSTNAME=foobar sudo ...` attack. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I tried to change sudoers to Defaults !lecture,tty_tickets,!fqdn and get the same sudo behavior, i. e. it warns, but does not fail. Thus I can still not reproduce the bug in Hardy. Can anyone else? -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I tried to reproduce this. I opened two terminal windows, and did sudo -i in one of them to get a root shell (#), the other is a normal user shell ($) $ sudo id [sudo] password for martin: uid=0(root) gid=0(root) Gruppen=0(root) 0 [EMAIL PROTECTED]:~ $ sudo -k so by default, sudo works. Now let's mangle the hostname: # hostname foobar On Dapper I now get: $ sudo id sudo: unable to lookup foobar via gethostbyname() while on current Hardy I get: $ sudo id sudo: unable to resolve host foobar [sudo] password for martin: uid=0(root) gid=0(root) Gruppen=0(root) i. e. it still warns me, but doesn't fail any more. Now, when I reset the hostname with # hostname `cat /etc/hostname` everything works again on both dapper and hardy. So this seems to be fixed for me. However, some of the recent duplicates (like bug 197494) seem to indicate that it is still a problem in hardy. I sanyone actually able to reproduce this? Can you please post a recipe here? For the record, I'm using the default sudoers: $ sudo grep -v '^#' /etc/sudoers | grep -v '^$' Defaultsenv_reset rootALL=(ALL) ALL %admin ALL=(ALL) ALL Or, asked the other way round, can you please check if it is fixed for you as well on current Hardy? Thanks in advance to all! ** Changed in: sudo (Ubuntu Hardy) Status: In Progress = Incomplete -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Hi Yesterday I did a dist-upgrade from gutsy, I haven't touched my sudoers file: sudo grep -v '^#' /etc/sudoers | grep -v '^$' Defaults!lecture,tty_tickets,!fqdn rootALL=(ALL) ALL %admin ALL=(ALL) ALL I found the bug and had to add a manual entry in etc/hosts: 127.0.0.1 cube This happens both on my laptop and desktop computer (both upgraded from gutsy to hardy) thanks -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Hi Changing Defaults !lecture,tty_tickets,!fqdn to Defaults env_reset and now it works as martin says thanks -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I have a wirless PCI card that is only partially supported in Ubuntu. During the installation and trial of drivers for that card, it has happened several times that sudo just stopped working, in the same manner as described here. This is highly frustrating. If I could touch /etc/sudo_only_on_this_machine, or something similar that would tell sudo that I was only using it on one machine, I would be happy. In fact, this should be the default. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
To clarify, the reason that sudo looks up the local hostname is that /etc/sudoers is designed to be shareable between multiple hosts. (/etc/hosts is too, but this doesn't work if you share an /etc/hosts that gives you no way to look up your own hostname.) In order to know which of the commands in /etc/sudoers are permitted on the present machine, you must be able to figure out which machine is the present machine. This can include the stacking of more specific *deny* rules together with rules that allow other access on all hosts; so even if sudo were fixed to be more lenient, the most lenient it could be is to discard all rules past the first non-ALL host spec. That doesn't prevent fixing this issue for the default Ubuntu /etc/sudoers, but it does show that the requirement for the host lookup is not spurious. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
I don't know how this sharing is supposed to be done, but whatever the usecase for it, denying user login because the local hostname cannot be resolved should definitely not be allowed here. The reason that I don't think you need to lookup the hostname is because the hostname is specified nowhere in the sudoers file, so it's wrong to simply lookup something that is not specified there. Perhaps it was easier to have a general approach of this matter, but you do have to admit the fact that sudo is looking up something that shouldn't be looked up. If we look a bit at the results (the machine being locked up for management, and a reboot required), I think that this general approach simply failed, and should be updated. Just my 0.02€. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Perhaps sudo should try to use the name from /etc/hostname when gethostbyname fails? It looks quite simple to do that, and assume that you'll have there 127:0.0.1 (in both IPv4 and v6)?!?!?! -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Changed in: sudo (Ubuntu) Importance: Low = High Status: Confirmed = In Progress -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
@harcesz The forums are a better place to get help. Launchpad is for reporting bugs when you find one. Nonetheless, you should be able to boot in rescue-mode and edit /etc/hostname and /etc/hosts files. If you need instructions on how to do this, use the forums. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
just updated to 8.04 and that either messed up my hostname or it's not good for sudo anymore, I'm a bit confused at the moment -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Yes,I just have experience this problem.And I come here for help,but I can't get help.If you had a solution,please tell me.Thanks. -- 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
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Changed in: sudo (Ubuntu) Assignee: (unassigned) = Martin Pitt -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://launchpad.net/bugs/32906 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Bug 62706 has been marked a duplicate of this bug -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://launchpad.net/bugs/32906 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
Another related bug: https://launchpad.net/bugs/19775 -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://launchpad.net/bugs/32906 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 32906] Re: sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on
** Bug 21859 has been marked a duplicate of this bug -- sudo shouldn’t ABSOLUTELY NEED to look up the host it’s running on https://launchpad.net/bugs/32906 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
