bugtraq - Re: RE: [Full-disclosure] Microsoft DNS resolver: deliberately sabotagedhosts-file lookup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060417123318.20887.qmail@securityfocus.com>
Date: 17 Apr 2006 12:33:18 -0000
From: john@...nsdomain.org
To: bugtraq@...urityfocus.com
Subject: Re: RE: [Full-disclosure] Microsoft DNS resolver: deliberately
 sabotagedhosts-file lookup

The XP DNS client has other problems as well.  It caches DNS failiures (arguably out of spec with the RFC, BTW), screwing up VPNs if you're VPNed into an internet network that has local domains which need to resolve to RFC1918 addresses.  The cached failed lookups get prefered to forced entries in the hosts file, if that is tried as a way of forcing the dns lookups to work.  Very frustrating.  So, this isn't much of a surprise.  Rotten, yes, surprising, no.