You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
, lines which contain the host name and which start with locahost or ::1 triggers control NAME-4406.
I fail to understand why the test checks for lines starting with locahost or ::1 instead of lines starting with 127.0.0.1 or ::1. Additionally, man hostname(1) states:
THE FQDN
…
The recommended method of setting the FQDN is to make the hostname be
an alias for the fully qualified name using /etc/hosts, DNS, or NIS.
For example, if the hostname was "ursula", one might have a line in
/etc/hosts which reads
127.0.1.1 ursula.example.com ursula
Technically: The FQDN is the name getaddrinfo(3) returns for the host
name returned by gethostname(2). The DNS domain name is the part after
the first dot.
Therefore it depends on the configuration of the resolver (usually in
/etc/host.conf) how you can change it. Usually the hosts file is parsed
before DNS or NIS, so it is most common to change the FQDN in
/etc/hosts.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Judging from
lynis/include/tests_nameservices
Line 618 in b53d6a8
, lines which contain the host name and which start with
locahost
or::1
triggers control NAME-4406.I fail to understand why the test checks for lines starting with
locahost
or::1
instead of lines starting with127.0.0.1
or::1
. Additionally, manhostname(1)
states:So isn't there a discrepancy in recommendations?
Thank you. :)
Beta Was this translation helpful? Give feedback.
All reactions