This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/4980] gethostbyname() etc break for /etc/hosts with both ::1 and 127.0.0.1 localhost entries
- From: "hyc at symas dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 1 Dec 2007 20:09:52 -0000
- Subject: [Bug libc/4980] gethostbyname() etc break for /etc/hosts with both ::1 and 127.0.0.1 localhost entries
- References: <20070829170356.4980.pasky@suse.cz>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From hyc at symas dot com 2007-12-01 20:09 -------
(In reply to comment #3)
> Stop reopening bugs. Search the web if you want an explanation, I don't have
> anything handy and certainly have no interest in writing it up.
I've found no discussion of this change on any of the glibc mailing list
archives, after searching through September-November 2006 on libc-announce,
libc-hacker, libc-alpha, glibc-cvs, or glibc-bugs. I think it's fair to say that
if you don't want people to keep asking stupid questions, a little more
documentation of your rationale will help.
The CVS log entry is useful, at least:
Support IPv6-style addresses for IPv4 queries if they
can be mapped.
But your implementation violates RFC2553: http://www.ietf.org/rfc/rfc2553.txt
Page 25:
Also note that the
IPv6 hex addresses "::" and "::1" MUST NOT be treated as IPv4-
compatible addresses, ...
Also for the macro in section 6.7 IN6_IS_ADDR_V4COMPAT MUST return
false for "::" and "::1".
I.e., the RFC specifically forbids the mapping of the IPV6 loopback address to
IPv4. As far as I can see, the current glibc behavior here is a bug.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4980
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.