From: John Darrington <john@darrington.wattle.id.au>
To: Hartmut Goebel <h.goebel@goebel-consult.de>
Cc: guix-devel@gnu.org
Subject: Re: Contents of /etc/hosts
Date: Sat, 8 Oct 2016 16:19:23 +0200 [thread overview]
Message-ID: <20161008141923.GB5979@jocasta.intra> (raw)
In-Reply-To: <57F62269.4090100@goebel-consult.de>
On Thu, Oct 06, 2016 at 12:07:37PM +0200, Hartmut Goebel wrote:
Am 06.10.2016 um 02:57 schrieb John Darrington:
> 127.0.0.1 localhost
> ::1 localhost
> 127.0.0.1 gambrinus
> ::1 gambrinus
>
> Or am I missing something?
>
> Hmm. I have never seen it done this way elsewhere, and I really wonder how some
> services will react if they discover that 127.0.0.1 is not called "localhost"?
> Or that one address is known by two names. I think it possible they might
> assume a security breach and refuse to work.
This should not be a problem. One could always add several entries for
the same IP-address. And "getent hosts 127.0.0.1" will return the first
entry in /etc/hosts AFAIKT.
I started digging through the man pages, but did not finish. It's a deep
maybe recursive mess of documentation where nothing is said about Maybe
we need to refer to the gethostbyname(2) and gethostbyname(3)
documentation, which both are listed in "man hostname".
Indeed it is a mess. And be careful there are several versions of "hostname" program
in circulation. One of them explicitly says that
127.0.1.1 canoncal-name.example.com canonical-name
Is the recommended way to set the canoncial name and fqdn
* gethostbyname(2) [1], uses uname[2], which returns what ever has been
set with sethostname (AFAICT) and always returns a single string.
That is also my understanding.
* gethostbyname(3) [3] returns a structure capable to hold an name,
several aliases, and several addresses.
Yes.
Nevertheless my conclusion is that any program should be able to handle
any ip-address and and hostname and must not rely on any assumtion
regarding these. (Exept perhaps to assume "localhost" is defined.)
Well behaved programs should not make such assumptions. But I don't think
we should assume that all programs behave well .
Anyway I think we need to change what we currently have because it breaks
"hostname -f" (and possibly other things too)
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
next prev parent reply other threads:[~2016-10-08 14:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 18:31 Contents of /etc/hosts John Darrington
2016-10-05 20:17 ` Ludovic Courtès
2016-10-06 0:57 ` John Darrington
2016-10-06 10:07 ` Hartmut Goebel
2016-10-08 14:19 ` John Darrington [this message]
2016-10-11 20:25 ` Ludovic Courtès
2016-10-06 9:24 ` Hartmut Goebel
2016-10-08 14:08 ` John Darrington
2016-10-09 9:12 ` Hartmut Goebel
2016-10-09 9:56 ` John Darrington
2016-10-09 10:53 ` Hartmut Goebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161008141923.GB5979@jocasta.intra \
--to=john@darrington.wattle.id.au \
--cc=guix-devel@gnu.org \
--cc=h.goebel@goebel-consult.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).