mirror of
https://github.com/nmap/nmap.git
synced 2026-08-04 14:49:29 +00:00
In Nsock, handle WSAEADDRNOTAVAIL (errno 10049) as a known connection error
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:
parent
96cc663799
commit
6f56ebfc22
1 changed files with 8 additions and 0 deletions
|
|
@ -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].
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue