This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug network/19791] res_query.c:262 asserts when dns contains unreachable entries


https://sourceware.org/bugzilla/show_bug.cgi?id=19791

--- Comment #9 from Florian Weimer <fweimer at redhat dot com> ---
Thanks.  I can reproduce it now.  I was running the test against the name
server from the reproducer, not a real-world nameserver.  I have not found the
root cause yet, though.

From what I can tell, the resolver is pretty much unusable in this
configuration (IPv6 addresses disabled, IPv6 name server configured). 
Supposedly successful DNS lookups do not return any data, and NXDOMAIN/NODATA
responses result in the reported assertion failure.  Does this match what you
see?

I assume you discovered this right after applying the patch because everything
stopped working.  Or was the failure more subtle?

(I'm asking these questions to determine if this constitutes a security bug in
its own right, rather than a regression exposed by a security fix.)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]