Re: Windows Nmap Port 0 problem

[kx <kxmail () gmail com>]

Well I would argue there are two points to a connect scan:

#1 - Use connect() because you are an unprivileged user
#2 - Complete a 3-way TCP handshake because it elicits different
behavior in an end host than a single SYN.

Port 0 is probably not a good case for this, and honestly connect
related issues seem to only pop up on windows, so I don't know what
utility it would be to the rest of the ports... just thinking out loud
I suppose.

- kx

On 4/3/07, Matthew Boyle <mb2263 () bristol ac uk> wrote:
> kx wrote:
> > Looks like our use of port 0 with connect ist verboten on Windows. I
> > would think we could use --send-eth to force Windows to use raw
> > ethernet so we could build our own headers, but it doesn't seem to
> > work. Honestly, I don't know the code well enough yet to know if nmap
> > has its own TCP connect stack, but it would be nice.
>
> i thought the whole point of the connect scan was that it used the OS's
> own system call, for times when manufacturing packets isn't an option?
>
> --matt
>
> --
> et je triche, et je mens, et je m'éclate, et je touche à tout.
>
>
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://SecLists.Org

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