sock:connect() returning messages incosistent with the docs

[Jacek Wielemborek <d33tah () gmail com>]

List,

While experimenting with Henri's nmap-nseportscan, I implemented 
connect() based port scanning in NSE. While trying to figure out 
when to mark port as closed and when as filtered, I noticed that 
the error messages I'm getting is either ERROR or FILTERED. 
Patrick pointed me to the root cause, which is the function 
nse_status2str defined in nsock/src/nsock_event.c being rather 
reticent. This function is being used in nse_nsock.cc:340.

I wouldn't be all that surprised with this result if it wasn't 
for the incosistency with the documentation it causes - have a 
look here:

http://nmap.org/nsedoc/lib/nmap.html#connect

How can we solve this problem - by updating the docs or making 
the error messages more verbose? I, for one, would find more 
meaningful messages quite useful.

Yours,
Jacek Wielemborek

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/