NSE script start/stop output

[David Fifield <david () bamsoftware com>]

With Patrick's permission, I committed his NSE output patch. A message
is printed when a script starts, stops, times out, or hits an error.  I
made all the messages include the script file name and the elapsed time.
Messages are printed with -d1 and at -d2 the thread ID (memory address)
is printed as well. It looks like

SCRIPT ENGINE (1.280s): Starting /usr/share/nmap/scripts/banner.nse against 192.168.0.1:23.
SCRIPT ENGINE (1.280s): Starting /usr/share/nmap/scripts/telnet-brute.nse against 192.168.0.1:23.
SCRIPT ENGINE (1.280s): Starting /usr/share/nmap/scripts/http-trace.nse against 192.168.0.1:80.
...
SCRIPT ENGINE (1.359s): Finished /usr/share/nmap/scripts/banner.nse against 192.168.0.1:23.
SCRIPT ENGINE (1.412s): Finished /usr/share/nmap/scripts/http-trace.nse against 192.168.0.1:80.
SCRIPT ENGINE (4.282s): Stopped /usr/share/nmap/scripts/telnet-brute.nse against 192.168.0.1:23 because of host timeout.

SCRIPT ENGINE (0.396s): Starting /usr/share/nmap/scripts/err.nse against 192.168.0.1.
SCRIPT ENGINE (0.396s): /usr/share/nmap/scripts/err.nse against 192.168.0.1 ended with error: Can't open socket

Here are a couple of ideas for enhancement: 1. Change "SCRIPT ENGINE" to
"NSE". 2. Print just the basename, not the whole path. With these
changes the output would be

NSE (1.280s): Starting banner.nse against 192.168.0.1:23.
NSE (1.280s): Starting telnet-brute.nse against 192.168.0.1:23.
NSE (1.280s): Starting http-trace.nse against 192.168.0.1:80.
...
NSE (1.359s): Finished banner.nse against 192.168.0.1:23.
NSE (1.412s): Finished http-trace.nse against 192.168.0.1:80.
NSE (4.282s): Stopped telnet-brute.nse against 192.168.0.1:23 because of host timeout.

NSE (0.396s): Starting err.nse against 192.168.0.1.
NSE (0.396s): err.nse against 192.168.0.1 ended with error: Can't open socket

David Fifield

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