[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v983fybu.fsf@quelaan>
Date: Fri, 30 Apr 2021 15:29:17 -0230
From: Julian Squires <julian@...ht.net>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: getaddrinfo/AI_ADDRCONFIG with ipv6 disabled
Rich Felker <dalias@...c.org> writes:
> So in light of this mess, the patch may be correct, despite the
> problem being misattributed, but it should probably also handle the
> EINVAL case. Also it's not 100% clear whether we should interpret this
> as "no IPv6" or ignore it as an access control policy rather than
> reflection of IPv6 existing. If there are any other ways the kernel
> can return EACCES or EINVAL here, we would not want to misinterpret
> that in a way that breaks IPv6.
I've sent an updated patch to the list. I did submit a change to
OpenWrt to not create these rules on devices where IPv6 is disabled:
https://patchwork.ozlabs.org/project/openwrt/patch/20210430143037.6763-1-julian@cipht.net/
but it seems to me that the patch to musl still makes sense, in as much
as these return codes from Linux make any sense at all.
<#secure method=pgpmime mode=sign>
--
Julian Squires
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.
