Re: "Windows does not support scanning your own machine (localhost) this way" shows all scanned ports

[Daniel Miller <bonsaiviking () gmail com>]

The todo states:

o When scanning your own IP from Windows, Nmap currently recognizes
  the problem (can't do a raw scan like that on Windows) and skips the
  SYN scan, leading to Nmap printing a bunch of ports in "unknown"
  state at the end.  Nmap should probably act like unprivileged mode
  in this case (e.g. do a connect scan, etc.).  See
  http://seclists.org/nmap-dev/2013/q3/519

I think this could also be remedied just on the output side of things
by using PORT_HIGHEST_STATE to indicate end-of-iteration for
PortList::nextIgnoredState instead of PORT_UNKNOWN. Since PORT_UNKNOWN
is a valid (sort of) state in this case, it results in never being
able to collapse them into an extraports element. PORT_HIGHEST_STATE
will never be a valid state, on the other hand.

I just don't think it would be good to pick a different scan mode than
what was requested in this case. I'm sure Windows doesn't support
scanning localhost with -sA, either: what would we fall back on in
that case?

Dan

On Sun, Sep 8, 2013 at 2:35 AM, Fyodor <fyodor () nmap org> wrote:
> On Wed, Sep 4, 2013 at 10:22 AM, <security () zarco nl> wrote:
>
> > When I scan my LAN with a Windows machine (behavior has been ever since
> > WinXP, now using Win8) and nmap has reached my Windows machine, I get the
> > error:
>
> Thanks for the report.  I can reproduce this by simply running "nmap
> [myownipaddress]" on Windows.  I will add an item about this to the Nmap
> todo file.
>
> Cheers,
> Fyodor
> _______________________________________________
> Sent through the dev mailing list
> http://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
http://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/