Re: Nmap SoC Ideas?

[Ron <ron () skullsecurity net>]

I've been keeping a wishlist lately, here's mine (let me know if you need clarification on anything):

o An option to 'pause' a scan. On my old connection, using excess bandwidth used to disconnect me from my PPPoE, and I 
wouldn't have a good way of killing Nmap temporarily so I didn't miss hosts. 
o Improved 'resume', where a scan can be stopped at any time and resumed with different options -- in particular, I 
often realize way too late in a scan that I forgot to specify -sV. Or, sometimes, I'll realize that I should be running 
a particular script that I didn't. 
o Along the same lines, persistent storage between scans. For example, I do a -p- and -sS of a /16. Then I look at 
which ports are open and decide to run script A, B, and C -- I'd like to go re-scan the hosts, but we already know 
which ones have the port open so we don't have to re-scan those
o Also on persistent storage, having a persistent registry could be useful. For example, I run all the *enum-users* 
scripts against a host, which save their discovered usernames to a persistent storage. Then I decide to run *brute* 
against them, perhaps with different options -- I'd like to be able to use the already discovered usernames
o 'auxiliary' scripts, in the same sense as auxiliary modules in Metasploit. Basically, scripts that run once, period. 
The biggest use of these is the ability to do broadcasted scripts, for NetBIOS, DHCP, etc
o Better script integration into Zenmap, such as parsing the @args fields for the scripts (and nselibs) to ask the user 
what they want to fill in (if anything). 
o A 'ranking' system for scripts, like Metasploit has for modules, and some intelligence in Zenmap that recommends 
scripts that might work against systems

Some of those are simple, and some of them might be too far from Nmap's paradigm to be included. But they're things 
that I've thought would be useful while running Nmap. 

On Sat, 13 Mar 2010 16:10:07 -0800 Fyodor <fyodor () insecure org> wrote:
> Hi Folks.  It is that time of the year again for the Summer of Code!
> I filled out the Google application yesterday.  Given that Nmap has
> been accepted for all five previous Summers of Code, chances are that
> we'll be accepted again.  But that is only the very beginning!  The
> most important work right now is identifying the projects we want
> accomplished this summer.  I already have some ideas, which I've
> posted here:
>
> http://nmap.org/soc/
>
> That page has all the details, but here is a summary of the projects:
>
> o Nmap Scripting Engine--Script Developer
> o Nmap Cloud Scanning Platform
> o Zenmap GUI Developer
> o Feature Creepers and Bug Wranglers
> o Nmap and Zenmap on Mobile Devices (iPhone, Android, Maemo, etc.)
> o Nmap Scripting Engine--Infrastructure manager
> o Ncrack Developer
> o Nping Developer 
>
> Those are all well and good, but I'd love to hear from the community
> where you would like Nmap to go!  This is your chance to specify a
> feature you've wanted and we may be able to find a college/grad
> student to get it done!  The Summer of Code lasts just under 3 months,
> but we can usually fit smaller tasks into larger projects (or "feature
> creeper" appointments), and we have a long history of large projects
> which take multiple years (Zenmap, NSE).
>
> We're even willing to consider separate applications as long as they
> fit with the rest of the Nmap suite.  After all, the latest SVN
> version of Nmap now offers 5 utilities: Nmap, Zenmap, Ndiff, Ncat, and
> (alpha version) Nping!  Plus we have the (alpha) Ncrack distributed
> from http://nmap.org/ncrack/.
>
> So let's hear your ideas!  I also welcome comments on the existing
> projects listed on the page.  Remember that even the best students are
> only as good (or at least as useful to the project) as the tasks we
> put them to.
>
> Cheers,
> Fyodor
> _______________________________________________
> Sent through the nmap-dev mailing list
> http://cgi.insecure.org/mailman/listinfo/nmap-dev
> Archived at http://seclists.org/nmap-dev/


-- 
Ron Bowes
http://www.skullsecurity.org
http://www.twitter.com/iagox86
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/