Nmap Development mailing list archives
Re: NSE Infrastructure: Eliminate script.db
From: Fyodor <fyodor () insecure org>
Date: Mon, 24 Mar 2008 13:49:59 -0700
On Mon, Mar 24, 2008 at 03:27:46PM -0500, Kris Katterjohn wrote:
Unfortunately, everytime I write a new script I have to set NMAPDIR and use -script-updatedb to update the script database in my nmap directory--for a lot of simple scripts this gets old :).
Hi Kris. Thanks for the suggestion. You are supposed to be able to do: nmap --script ./mynewscript.nse Is that not working for you? You shouldn't need to add it to the DB unless you want to call it by category.
I was thinking that Nmap could use the steps it takes to build the database file, but instead of writing to the script.db it could just build the internal list of scripts (or however it works--I'm not well-versed in the innards of NSE). This would eliminate the - -script-updatedb option and the script.db.
Well, we added the script.db for efficiency reasons. It may not make a huge difference now, but it might start to as the number of scripts continues to grow. I believe Diman did some testing with 10,000 scripts. Right now we only have about 50, but the system is still new. Nessus has more than 21,000 plugins. Cheers, -F _______________________________________________ Sent through the nmap-dev mailing list http://cgi.insecure.org/mailman/listinfo/nmap-dev Archived at http://SecLists.Org
Current thread:
- NSE Infrastructure: Eliminate script.db Kris Katterjohn (Mar 24)
- Re: NSE Infrastructure: Eliminate script.db Brandon Enright (Mar 24)
- Re: NSE Infrastructure: Eliminate script.db Kris Katterjohn (Mar 24)
- Re: NSE Infrastructure: Eliminate script.db Fyodor (Mar 24)
- Re: NSE Infrastructure: Eliminate script.db Kris Katterjohn (Mar 24)
- Re: NSE Infrastructure: Eliminate script.db Brandon Enright (Mar 24)