From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: getaddrinfo usage with wrong ip family
Date: Thu, 24 Sep 2015 12:59:01 +0200 [thread overview]
Message-ID: <20150924105901.GI10551@port70.net> (raw)
In-Reply-To: <71B72D33-A1D4-4B23-BFEB-6BFA01DF7523@gmail.com>
* Julien Ramseier <j.ramseier@gmail.com> [2015-09-24 12:27:22 +0200]:
> > Le 22 sept. 2015 à 17:16, Rich Felker <dalias@libc.org> a écrit :
> >
> > Another approach might be having __lookup_numeric always parse with
> > AF_UNSPEC, but return error rather than 0 results if the resulting
> > family does not match the requested family.
>
> This seems the simplest solution in the meantime.
>
> Here???s the patch I applied to my trunk.
>
forgot to attach the patch?
next prev parent reply other threads:[~2015-09-24 10:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 14:40 Julien Ramseier
2015-09-22 15:16 ` Rich Felker
2015-09-24 10:27 ` Julien Ramseier
2015-09-24 10:59 ` Szabolcs Nagy [this message]
2015-09-24 15:11 ` Julien Ramseier
2015-09-24 15:39 ` Rich Felker
2015-09-25 1:48 ` Rich Felker
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150924105901.GI10551@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.com \
/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.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).