Re: NMAP crash

[starlight.2012q3 () binnacle cx]

Disagree.

This is what it looks like when -S works
correctly and all traffic flows along
the correct path.




At 02:03 PM 9/13/2012 -0700, David Fifield wrote:
> On Thu, Sep 13, 2012 at 03:08:32AM -0400, 
> starlight.2012q3 () binnacle cx wrote:
> > Came upon a reproducible crash that
> > might be of interest.  Running SVN 29768.
> >
> > Command is
> >
> >   nmap -e eth4 -S 172.29.86.4 --send-eth \
> >        -T4 -Pn -O -sV -sC 58.218.199.227
> >
> > also happens with target 58.218.199.250
>
> I don't think this is so mysterious. The target is responding 
> with a
> SYN/ACK to every SYN probe, whether the port is open or not. 
> Sometimes
> satellite systems or other firewalls do this to reduce latency.
>
> http://seclists.org/nmap-dev/2009/q2/556
>
> Running out of sockets appears to happen later, during the 
> script
> scanning phase. It is possible that sockets are not being closed
> properly somewhere in this error condition.
>
> David Fifield

Attachment: nmap_good.txt
Description:

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