Nmap Development mailing list archives

Re: New Script Ideas (and Authors) Wanted!


From: "Littlefield, Tyler" <tyler () tysdomain com>
Date: Mon, 09 Jan 2012 09:47:33 -0700

Hello:
I've had a few years of experience with programming, but NMAP is a new deal for me. I always have it installed and use it for the most basic of port scans, usually a host discovery across a network, but I would like to use my programming skills to help out the project.

This said:
1) Is there anyone that would be willing to mentor me at least a bit, help me find things I could work on that are entry-level and would help me get a better understanding of nmap while also contributing to the project? 2) Should someone not have the time to mentor, ideas for entry-level projects (preferably small for the time being) would be awesome.
On 12/20/2011 4:51 PM, Fyodor wrote:
Hi folks!  The Nmap Script Ideas page has been a big success and we've
ended up writing many of the scripts that people have added there.  So
many, in fact, that we're running out of good ideas!  So this is a
call out for folks to think about what functionality you'd really like
Nmap to have, and then add your clever, useful ideas to the wiki page:

https://secwiki.org/w/Nmap_Script_Ideas

Add them to the incoming section for now, and they will be reviewed
and prioritized later.

Here are some factors which make a script particularly valuable:

o It is appropriate for the default category (you can read about what
   makes a good default script at
   http://nmap.org/book/nse-usage.html#nse-categories).

o The results serve a common and practical purpose.  In other words it
   produces valuable and actionable information or actions.  You should
   be able to easily explain why a network/security administrator or
   other user would want to do this.

o Common--a script which interrogates an extremely common service is
   far more valuable than one which queries a service that is almost
   never available.

o Speed--great scripts are optimized for speed--they don't leave the
   user waiting any longer than necessary.

A good rule of thumb is that if you think the feature would be very
useful for your Nmap scans, others probably would like it too.
Scripts don't have to meet all of these factors--just strike a good
balance.

If you have any good ideas, please add them to the page!

Of course thinking up ideas is only part of the battle.  We're always
looking for folks to actually write scripts too.  And if you don't
know where to start, take a look at that same script ideas page for
inspiration:

https://secwiki.org/w/Nmap_Script_Ideas

After you write and test a script, please send it to nmap-dev for
discussion and potential inclusion into Nmap.

In just the last year we've gone from 161 scripts to 294!  That is
extraordinary, and I'm hoping we can keep up that momentum.

Cheers,
Fyodor
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/


--

Take care,
Ty
Web: http://tds-solutions.net
The Aspen project: a light-weight barebones mud engine
http://code.google.com/p/aspenmud

Sent from my toaster.

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


Current thread: