Re: [NSE] scan traceroute hops

[Djalal Harouni <tixxdz () gmail com>]

On 2010-09-06 19:48:13 +0200, Henri Doreau wrote:
> Concerning the target.add() feature, I faced a behavior I wasn't
> expecting. If I try to add the current host.ip to the queue, it will
> work once and then fail.
> This is reproducible with the attached script and the command line :
>
> # ./nmap --datadir . --script add-self -sP -v --script-args newtargets
> scanme.insecure.org
>
> Is this behavior expected? Am I missing something?
Yes this is the plan. We filter the same added strings targets to avoid
infinite loop scans, since portrule and hostrule scripts can run
multiple times during a scan and if they keep adding the same strings
targets then the scan would not end, and in your case Nmap would
continue to run against scanme.nmap.org

To get a better debug messages pls update your svn copy and run with -d3,
the output should be:

Starting Nmap 5.35DC18 ( http://nmap.org ) at 2010-09-06 23:04 CET
...
NSE: Script Pre-scanning.
Fetchfile found ./nmap-payloads
Initiating Ping Scan at 23:04
Scanning scanme.nmap.org (64.13.134.52) [2 ports]
CONN (0.2410s) TCP localhost > 64.13.134.52:80 => Operation now in progress
CONN (0.2410s) TCP localhost > 64.13.134.52:443 => Operation now in progress
...
NSE: Script scanning 64.13.134.52.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 23:04
NSE: NSE Script Threads (1) running:
NSE: Starting 'add-self' (thread: 0x989cf78) against 64.13.134.52.
New Targets: target 64.13.134.52 pushed onto the queue.
NSE: ADD-SELF: Added new target 64.13.134.52
NSE: Finished 'add-self' (thread: 0x989cf78) against 64.13.134.52.
NSOCK (5.2430s) nsock_loop() started (timeout=50ms). 0 events pending
Completed NSE at 23:04, 0.00s elapsed
Nmap scan report for scanme.nmap.org (64.13.134.52)
Host is up, received syn-ack (0.37s latency).
Final times for host: srtt: 370000 rttvar: 370000  to: 1850000

doing 0.0.0.0 = 64.13.134.52
Initiating Ping Scan at 23:04
Scanning 64.13.134.52 [2 ports]
CONN (5.2440s) TCP localhost > 64.13.134.52:80 => Operation now in progress
CONN (5.2440s) TCP localhost > 64.13.134.52:443 => Operation now in progress
...
Overall sending rates: 0.72 packets / s.
NSE: Script scanning 64.13.134.52.
NSE: Starting runlevel 1 (of 1) scan.
Initiating NSE at 23:04
NSE: NSE Script Threads (1) running:
NSE: Starting 'add-self' (thread: 0x98ce320) against 64.13.134.52.
New Targets: target 64.13.134.52 is already in the queue.
NSE: failed to add new targets.
NSE: ADD-SELF: failed to add new targets.
NSE: Finished 'add-self' (thread: 0x98ce320) against 64.13.134.52.
NSOCK (9.4330s) nsock_loop() started (timeout=50ms). 0 events pending
Completed NSE at 23:04, 0.00s elapsed
Nmap scan report for scanme.nmap.org (64.13.134.52)
Host is up, received syn-ack (0.32s latency).
Final times for host: srtt: 318000 rttvar: 318000  to: 1590000

NSE: Script Post-scanning.
Read from .: nmap-payloads.
Nmap done: 2 IP addresses (2 hosts up) scanned in 9.44 seconds


Thx for the tests and let us know if you have other suggestions.

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