Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 10 Jul 2018 21:01:19 -0400
From: Christopher Friedt <chrisfriedt@...il.com>
To: musl@...ts.openwall.com
Subject: Re: getaddrinfo(3) / AI_ADDRCONFIG

On Tue, Jul 10, 2018 at 8:38 PM Rich Felker <dalias@...c.org> wrote:
> Regardless of what's done on the musl side, I think it would make
> sense for thrift to change its strategy for selecting an address to

Let's take thrift out of the equation and read the POSIX spec.
Directrly from [1]:

"If the AI_ADDRCONFIG flag is specified, IPv4 addresses shall be
returned only if an IPv4 address is configured on the local system,
and IPv6 addresses shall be returned only if an IPv6 address is
configured on the local system."

There are precisely zero IPv6 addresses configured on the local
system. There is precisely two IPv4 address configured on the local
system (127.0.0.1, and 172.17.0.2 in this case).

Regardless of whether loopbacks are ignored, you are breaking POSIX
spec with your current implementation. Period.

Regards,

C

[1] http://pubs.opengroup.org/onlinepubs/9699919799/functions/getaddrinfo.html

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.