SUDO UNABLE TO RESOLVE HOST BPC UPDATE
(My guess, based on experience, would be that when you changed the IP address and/or hostname of your current host, but you neglected to update /etc/hosts and/or didn't add a DNS entry for your new FQDN in whatever DNS server your network considers authoritative in this manner.
That said, being unable to look up its own name may not be a security issue by itself, but that is a thing it should be able to do, and it would be wise to try and find out why it can't, just in case the error is masking a bigger problem. I dont know what happened Cant seem to edit /etc/hosts in su or sudo vim or sudo nano (Im only trying to edit this file because I think its the cause of the issue below) always get either sudo: unable to resolve hostSo you're very likely safe - as far as sudo is concerned, at least. You will need to use a live session since /etc/hosts needs sudo to be able to save changes ( sudo nano /etc/hosts) and if sudo complains. You need to alter the 2nd word on the 2nd line to 127.0.0.1 linux98. Note that, like most security conscious software, sudo fails safe - if it can't look up the host, any entry that specify a host value is considered invalid. 1 That error shows up if you changed host name and /etc/hosts was not changes.
However, because that component still exists, sudo does a lookup for the current hostname to see if it may or may not match against any hypothetical entries in the sudoers file that might tell it whether or not to permit this sudo attempt.
This has mostly fallen into disuse these days, but it was a way to keep the same sudoers file identical across multiple servers without having to tweak it for every single host. TL DR: Almost certainly none, but mind the qualifier.Īs man sudoers explains, there is room in a sudoers entry for a 'host' specification.
0 kommentar(er)
