sudo -h localhost
Marc Haber <[email protected]> Tue, 1 Jul 2025 06:03:45 +0200
| Newsgroups | gmane.comp.tools.sudo.user |
|---|---|
| Message-ID | <[email protected]> |
We all know that sudo complains about unresolvable host names when used on a system that doesn't have access to proper DNS and/or its host name not being clear. I have not quite understood in which circumstances that happens and have happily ever ignored that message, albeit annoying. I have recently learned that some people use sudo -h localhost to get around this message and to keep sudo silent. Reading the man page: | -h host, --host=host | Run the command on the specified host if the security policy | plugin supports remote commands. The sudoers plugin does not | currently support running remote commands. This may also be used | in conjunction with the -l option to list a user's privileges | for the remote host. I guess this is taking advantage of undocumented behavior (ths sudoers plugin has never officially supported -h). Well, this undocumented behavior has changed with the recent security update. Can sudo offer a different way to get rid of the "can't resolve host" error message? Quite a lot of Debian's QA processes run without network. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421 ____________________________________________________________ sudo-users mailing list <[email protected]> For list information, options, or to unsubscribe, visit: https://www.sudo.ws/mailman/listinfo/sudo-users