Home page logo
/

nmap-dev logo Nmap Development mailing list archives

stdnse.print_debug() enhancements
From: Lionel Cons <lionel.cons () cern ch>
Date: Fri, 21 Dec 2007 12:25:12 +0100

stdnse.print_debug() is great to debug scripts. However, when scanning
several targets at the same time, it is impossible to find out which
debug line corresponds to which instance of which script.

I would suggest to improve the debug lines reported by Nmap to include:
 - the script name (either the file name or its declared "id")
 - a script instance id (a kind of pid)

Also, at the start of the invocation, Nmap could report which host and
port correspond to a given script id.

So, instead of seing:

 Initiating SCRIPT ENGINE at 11:58
 SCRIPT ENGINE DEBUG: hello world
 SCRIPT ENGINE DEBUG: hello world
 SCRIPT ENGINE DEBUG: hello world
 SCRIPT ENGINE DEBUG: hello world
 Completed SCRIPT ENGINE at 11:58, 3.17s elapsed

we could see something like:

 Initiating SCRIPT ENGINE at 11:58
 SCRIPT ENGINE DEBUG: started [test1.1] against target1 port nil
 SCRIPT ENGINE DEBUG: started [test1.2] against target3 port nil
 SCRIPT ENGINE DEBUG: started [test2.3] against target2 port udp/123
 SCRIPT ENGINE DEBUG: started [test2.4] against target1 port udp/234
 SCRIPT ENGINE DEBUG: [test2.3] hello world
 SCRIPT ENGINE DEBUG: [test1.2] hello world
 SCRIPT ENGINE DEBUG: [test1.1] hello world
 SCRIPT ENGINE DEBUG: [test2.4] hello world
 Completed SCRIPT ENGINE at 11:58, 3.17s elapsed

If you're afraid of the amount of lines produced, this could be
displayed only if debug > 1...

Cheers,

Lionel Cons

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


  By Date           By Thread  

Current thread:
  • stdnse.print_debug() enhancements Lionel Cons (Dec 21)
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]