Re[2]: mirc32 6.0x crash when resolving dns.
From: 3APA3A (3APA3A_at_SECURITY.NNOV.RU)
Date: 05/28/03
- Previous message: at4r ins4n3: "Re: mirc32 6.0x crash when resolving dns."
- In reply to: Davide Del Vecchio: "Re: mirc32 6.0x crash when resolving dns."
- Next in thread: Peter Pentchev: "Re: mirc32 6.0x crash when resolving dns."
- Reply: Peter Pentchev: "Re: mirc32 6.0x crash when resolving dns."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 28 May 2003 14:45:25 +0400 To: vuln-dev@securityfocus.com
Dear Davide Del Vecchio,
Currently 210.193.16.25 doesn't resolve. But during original test it had
flowed PTR record:
bash-2.03$ host 210.193.16.25
25.16.193.210.IN-ADDR.ARPA is a nickname for 25.16.16.193.210.IN-ADDR.ARPA
(.16 is twice)
PTR doesn't resolve back:
bash-2.03$ host 25.16.16.193.210.IN-ADDR.ARPA
Host not found, try again.
Probably this bug may present if host has unresolvable PTR record.
I don't use mirc and can't confirm it.
--Wednesday, May 28, 2003, 1:57:45 AM, you wrote to at4r@3wdesign.es:
DDV> -
DDV> [23:57] * Unable to resolve 210.193.16.25
DDV> -
DDV> [23:57] * Unable to resolve 210.193.16.26
DDV> -
>> /dns 210.193.16.25
>> * Looking up 210.193.16.25
>> * Unable to resolve 210.193.16.23
>> (** MIRC CRASH**)
>>
-- ~/ZARAZA Машина оказалась способной к единственному действию, а именно умножению 2x2, да и то при этом ошибаясь. (Лем)
- Previous message: at4r ins4n3: "Re: mirc32 6.0x crash when resolving dns."
- In reply to: Davide Del Vecchio: "Re: mirc32 6.0x crash when resolving dns."
- Next in thread: Peter Pentchev: "Re: mirc32 6.0x crash when resolving dns."
- Reply: Peter Pentchev: "Re: mirc32 6.0x crash when resolving dns."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|