Re: Nmap Port 0 problem

[David Matousek <david () matousec com>]

Hi,

Well the problem is not that it fails since the OS call fails.
The problem is that Nmap goes to an infinite loop and reports errors
that are not understandable. Simply said, end-user should never see
something like "Unknown error" or "Strange read error". And in this context
"No such file or directory" is also bad.
The correct behaviour would be if the appropriate message was shown
and only once and then Nmap should terminate.
Of course that fixing this to make it working or handle it somehow
would be better, but just write error message and quit would be good enough.

David

Andrew Lutomirski wrote:
> On 4/2/07, David Matousek <david () matousec com> wrote:
> > Hi,
> >
> > running "nmap -P0 -p0 -sT 1.2.3.4" on Windows machines (tested on 2000 
> > and 2003 with Nmap 4.11
> > and 2000 with Nmap 4.21ALPHA4) causes some strange reports like
> >
> > "Strange read error from 1.2.3.4 (10049 - 'Unknown error'): No such 
> > file or directory"
>
> This is WSAEADDRNOTAVAIL, which sounds like correct behavior to me.
> We could do better on the error message, though (we clearly have a bug
> in whatever generated 'Unknown error' since this is a standard error
> code).
>
> I'm surprised this works on Linux.
>
> > If any other port is used instead of 0, it works fine, if P0 is not 
> > specified, it appears only if
> > the machine is alive, if -sT is not specified, it works fine.
>
> -sS should just work.
>
> --Andy

_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://SecLists.Org