public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/12154] Cannot resolve hosts which have wildcard aliases
Date: Wed, 21 Sep 2022 18:01:30 +0000 [thread overview]
Message-ID: <bug-12154-131-9yqhsLBn5P@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12154-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12154
--- Comment #25 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.34/master branch has been updated by Florian Weimer
<fw@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=c36e7cca3571b0c92b09409c1df86a142596c210
commit c36e7cca3571b0c92b09409c1df86a142596c210
Author: Florian Weimer <fweimer@redhat.com>
Date: Tue Aug 30 10:02:49 2022 +0200
nss_dns: In gaih_getanswer_slice, skip strange aliases (bug 12154)
If the name is not a host name, skip adding it to the result, instead
of reporting query failure. This fixes bug 12154 for getaddrinfo.
This commit still keeps the old parsing code, and only adjusts when
a host name is copied.
Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
(cherry picked from commit 32b599ac8c21c4c332cc3900a792a1395bca79c7)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-21 18:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:17 [Bug libc/12154] New: Can not resolve chained CNAME with a wildcard among the chained CNAME vincent.viallet at gmail dot com
2010-10-22 14:51 ` [Bug libc/12154] " vincent.viallet at gmail dot com
2010-11-20 14:21 ` pasky at suse dot cz
2012-02-21 2:11 ` [Bug network/12154] " jsm28 at gcc dot gnu.org
2012-12-19 10:45 ` schwab@linux-m68k.org
2014-06-30 7:23 ` fweimer at redhat dot com
2022-07-04 16:17 ` [Bug network/12154] Cannot resolve hosts which have wildcard aliases fweimer at redhat dot com
2022-08-10 9:35 ` fweimer at redhat dot com
2022-08-30 8:04 ` cvs-commit at gcc dot gnu.org
2022-08-30 8:04 ` cvs-commit at gcc dot gnu.org
2022-08-30 8:15 ` fweimer at redhat dot com
2022-08-31 1:34 ` vincent.viallet at gmail dot com
2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org
2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org
2022-09-13 11:24 ` cvs-commit at gcc dot gnu.org
2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org
2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org
2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org
2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org [this message]
2024-02-26 21:31 ` fw at deneb dot enyo.de
2024-02-27 11:07 ` fw at deneb dot enyo.de
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=bug-12154-131-9yqhsLBn5P@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).