Nmap Development mailing list archives
Re: nmap (win32 4.60) bug and a fix
From: Fyodor <fyodor () insecure org>
Date: Tue, 8 Apr 2008 17:07:39 -0700
On Mon, Mar 31, 2008 at 03:21:32PM +0300, Dudi I wrote:
Hi, I found a problem with nmap (4.60) when running on win32. when i scan an ip address which is a broadcast address (like 192.169.1.255) nmap gets into an infinite loop. its seems that the return code from getsockopt in this case is not handled at all (a 'Strange read error ...' message is produced) and nmap gets into an infinite loop. Attached is the diff file to fix this issue.
Thanks Dudi. I've applied this for the next Nmap release. -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- Re: nmap (win32 4.60) bug and a fix Fyodor (Apr 08)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 09)
- Re: nmap (win32 4.60) bug and a fix DePriest, Jason R. (Apr 09)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 11)
- Re: nmap (win32 4.60) bug and a fix Dudi I (May 04)
- Re: nmap (win32 4.60) bug and a fix DePriest, Jason R. (Apr 09)
- Re: nmap (win32 4.60) bug and a fix Ionreflex (Apr 09)