RE: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-19 Thread Mario Contestabile
@lists.grok.org.uk; bugtraq@securityfocus.com Subject: Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup On Thu, Apr 13, 2006 at 06:29:15PM +0100, Dave Korn wrote: Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-14 Thread imipak
Nick FitzGerald wrote: So, the exception is not that the IP is hard-coded, but that the DNS resolver skips looking in hosts for that _domain_ and necessarily does a network DNS lookup... Presumably, it uses whichever DNS server the local OS thinks it should use, no differently than any

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-14 Thread Vidar Løkken
On Fri, 14 Apr 2006, imipak wrote: Nick FitzGerald wrote: So, the exception is not that the IP is hard-coded, but that the DNS resolver skips looking in hosts for that _domain_ and necessarily does a network DNS lookup... Unless the DNS server is itself hardcoded in MediaPlayer, as well?

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-14 Thread Jurjen Oskam
On Fri, Apr 14, 2006 at 06:00:23PM +0200, Vidar L?kken wrote: So, the exception is not that the IP is hard-coded, but that the DNS resolver skips looking in hosts for that _domain_ and necessarily does a network DNS lookup... Unless the DNS server is itself hardcoded in MediaPlayer, as

[Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread Dave Korn
Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts table lookup functionality. Normally you can override DNS lookup by specifying a hostname and IP directly in the hosts file, which is searched before any query is issued to your dns server;

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread Brandon S. Allbery KF8NH
On Apr 13, 2006, at 1:29 , Dave Korn wrote: Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts table lookup functionality. I thought this was part of avoiding malware attempts to block Windows Update. -- brandon s. allbery

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread John Doe
I don't even get the same IP address for that. I have 64.4.52.189 . I tried to change it in the host files with the same results. Next I will block that IP in my firewall and see what happens. Ducki3 On 4/13/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: hi,...makes me wonder what happens

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread Stan Bubrouski
On 4/13/06, Brandon S. Allbery KF8NH [EMAIL PROTECTED] wrote: On Apr 13, 2006, at 1:29 , Dave Korn wrote: Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts table lookup functionality. I thought this was part of avoiding malware attempts

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread A . L . M . Buxey
hi, ...makes me wonder what happens if/when they need to change the IP address of go.microsoft.com many many people have already been burnt by the hardcoding of addresses/IPs into their applications. a ___ Full-Disclosure - We believe in it.

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread dumdidumdideldey
hi [EMAIL PROTECTED] wrote: hi, ...makes me wonder what happens if/when they need to change the IP address of go.microsoft.com many many people have already been burnt by the hardcoding of addresses/IPs into their applications. thats the point. its not the ip which is hardcoded. its the

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread Joachim Schipper
On Thu, Apr 13, 2006 at 06:29:15PM +0100, Dave Korn wrote: Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts table lookup functionality. (...) I'd try to block (Windows Media Player) it in my hosts file. Microsoft DNS client

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread J.A. Terranson
On Thu, 13 Apr 2006, Brandon S. Allbery KF8NH wrote: On Apr 13, 2006, at 1:29 , Dave Korn wrote: Hey, guess what I just found out: Microsoft have deliberately sabotaged their DNS client's hosts table lookup functionality. I thought this was part of avoiding malware attempts to block

Re: [Full-disclosure] Microsoft DNS resolver: deliberately sabotaged hosts-file lookup

2006-04-13 Thread Nick FitzGerald
John Doe wrote: I don't even get the same IP address for that. I have 64.4.52.189 . I tried to change it in the host files with the same results. Next I will block that IP in my firewall and see what happens. Think load-balancing, dynaminc content distribution hosting, etc. A... So, the