Ubuntu
sudo package

  1. Bug #32906
  2. Comment #18

Comment 18 for bug 32906

Revision history for this message
B. Clausius (barcc) wrote : 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
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