mailing list archives
Re: [NSE] How brute scripts and UN/PW scripts interact with creds
From: Brendan Byrd <sineswiper () gmail com>
Date: Wed, 28 Dec 2011 07:01:35 -0500
On Sun, Dec 25, 2011 at 4:33 PM, Patrik Karlsson <patrik () cqure net> wrote:
I'm guessing by long-term you mean that they are not stored once Nmap
As for script interaction, the library was added not that long ago and all
scripts that make use of the brute library implicitly use it.
But there is some work left of migrating old brute scripts to the brute
framework and adding the cred library to those that could use it. As for
saveToFile function there was one added by Tom Sellers 2011/09/04, but it
doesn't appear in the nsedoc due to a formatting issue.
Yeah, I started that route, but ended up with a creds-db.nse script. It's
a prerule/postrule script that loads/saves the existing creds DB data into
a permanent file. I'll submit it as soon as I get this snmp-brute stuff
There's also the matter of database size. Is the Lua code fast enough to
look through, say, 10K hosts in a Lua table among thousands of script
checks? If not, then some sort of mini-database format, or maybe a better
type of lookup, would need to be created.
Just to get a better understanding, could you provide me with a use case
Sure. I'm scanning a couple thousand hosts to ID them via SNMP. These
hosts potentially use one of 7-8 community strings. Instead of doing 7-8
NMap scans on each community string, I want to be able to figure out the
right community string for each host and then do version checking on them
all to get the SNMP hostname. This might turn into 2 NMap scans (one for a
community string find, and the larger one for basic scanning/ID of the
hosts), but it's better than parsing through 7-8 different XML files.
I got mostly everything working and figured out my looping bugs so far, but
I'm still occasionally hitting a freeze problem with certain hosts on
snmp-brute. Of course, since creds-db only saves at the very end of the
NMap run, this wastes all of the work previously and I have to debug and
start over again. I really wish NMap would wake up and realize that a
script is endlessly looping, but I guess that's up to us to debug.
Brendan Byrd/SineSwiper <SineSwiper () GMail com>
Sent through the nmap-dev mailing list
Archived at http://seclists.org/nmap-dev/