From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 32578 invoked from network); 27 Jun 2022 14:06:43 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 27 Jun 2022 14:06:43 -0000 Received: (qmail 15699 invoked by uid 550); 27 Jun 2022 14:06:41 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 15667 invoked from network); 27 Jun 2022 14:06:40 -0000 Date: Mon, 27 Jun 2022 10:06:27 -0400 From: Rich Felker To: Markus Geiger Cc: musl@lists.openwall.com Message-ID: <20220627140627.GS7074@brightrain.aerifal.cx> References: <20220624145936.GP7074@brightrain.aerifal.cx> <20220625015655.GR7074@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] [BUG] Non-FQDN domain resolving failure on musl-1.2.x On Mon, Jun 27, 2022 at 01:35:50PM +0200, Markus Geiger wrote: > Hi, > > 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 > network/lookup_name.c:166 > 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. Rich