I can reproduce the bug in Hardy:
barcc:~$ sudo grep -v '^#' /etc/sudoers | grep -v '^$'
Defaults !lecture,tty_tickets,!fqdn,timestamp_timeout = 15
root ALL=(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
root ALL=(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
