PenTest/nmap
1
0
Fork 0
mirror of https://github.com/nmap/nmap.git synced 2026-01-19 04:39:01 +00:00
Code Issues Projects Releases Wiki Activity

In Nsock, handle WSAEADDRNOTAVAIL (errno 10049) as a known connection error

Browse Source 
rather than allowing an assertion failure. This error code is sometimes
returned by Windows when attempting to scan a broadcast address or port 0.
This commit is contained in:
david
2009-01-14 20:16:25 +00:00
parent 96cc663799
commit 6f56ebfc22
1 changed files with 8 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
CHANGELOG
View File

@@ -1,5 +1,13 @@
# Nmap Changelog ($Id$); -*-text-*-
o Nsock handles a certain Windows connect error, WSAEADDRNOTAVAIL
(errno 10049), preventing an assertion failure that looked like
Strange connect error from 203.65.42.255 (10049): No such file or directory
Assertion failed: 0, file .\src\nsock_core.c, line 290
The error could be seen by running a version scan against a
broadcast address. Thanks to Tilo Köppe and James Liu for reporting
the problem. [David]
o NSE prints messages in debugging mode whenever a script starts or
finishes [Patrick, David].