From: Rich Felker <email@example.com>
To: Markus Geiger <firstname.lastname@example.org>
Subject: Re: [musl] [BUG] Non-FQDN domain resolving failure on musl-1.2.x
Date: Mon, 27 Jun 2022 10:06:27 -0400 [thread overview]
Message-ID: <20220627140627.GS7074@brightrain.aerifal.cx> (raw)
On Mon, Jun 27, 2022 at 01:35:50PM +0200, Markus Geiger wrote:
> Thanks for the info. I'm not a everyday gdb user (once a year?) – but
> I debugged the issue.
> In musl 1.2.2 we run into EAI_AGAIN in name_from_dns on
> In musl 1.1.24 we don't.
> Just that I'm not quite sure if that behavior is correct – if you can
> verify that it is correct behaviour treat this issue as resolved. And
> thX for looking into it.
Yes, that behavior is correct. The responses were inconclusive and
returning success as if they were conclusive is a DNSSEC-bypass bug
that was fixed.
prev parent reply other threads:[~2022-06-27 14:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 10:28 Markus Geiger
2022-06-24 14:59 ` Rich Felker
2022-06-24 15:10 ` Jeffrey Walton
2022-06-24 15:15 ` Rich Felker
2022-06-24 17:14 ` Markus Geiger
2022-06-25 1:56 ` Rich Felker
2022-06-27 11:35 ` Markus Geiger
2022-06-27 14:06 ` Rich Felker [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).