Re: NSE script start/stop output

[David Fifield <david () bamsoftware com>]

On Tue, Jan 06, 2009 at 10:28:25PM -0600, Kris Katterjohn wrote:
> > 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
>
> I like both of these ideas.

Fyodor already made the "NSE" change and I made the debug messages use
script ids in r12156. The output looks like what's above, without ".nse"
extensions.

David Fifield

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