From 6f56ebfc22f920279987b7e507fd6fe9eaa309a0 Mon Sep 17 00:00:00 2001 From: david Date: Wed, 14 Jan 2009 20:16:25 +0000 Subject: [PATCH] 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. --- CHANGELOG | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CHANGELOG b/CHANGELOG index 887c7213f..e559db26a 100644 --- a/CHANGELOG +++ b/CHANGELOG @@ -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].