PROJECT GOALS:

	To support Marty and Co's fine work with the Snort IDS tool by
providing an easy to use interface to make it more friendly to the 'newbies'
who tend to choke up over text file editing, confusing options, and so on
and so forth.  In short, to make Snort easy to configure and use for the 
un-initiated.

	Anyone who wants to contribute code to this effort, please feel free
to chip in.  I'm more than happy to give credit where it's due (your name
in lights!), and of course, I'm always happy to have working code that I 
didn't have to write myself. :)

	So, on with the TODO list:


1.  Code cleanup!!!! Ack some of this is downright UGLY!  I was a bit too 
quick to "make it work" and a bit too slow on the "think it through", and
it shows.  :(  Parts of this have already been done, but the majority of 
it is still "first draft while coding at full tilt typing speed while 
ingesting lots of coffie" grade code, and should be cleaned up for style, 
consistency, efficiency, and easy code re-use as the project develops.

	(Sections between BEG and END should be completed and removed from
this file prior to 0.4.x release).

BEG*************************************************************************
2.  Steal a bunch of stuff from snort's config file code so's we can use 
existing snort.conf files as a template (so's we can manage rules files, 
not just write them).

3.  Write facilities for a snortconf.conf file so's we can have site 
defaults (where to find rules files, where to write output, etc) instead 
of making user figure this out at compile time or accept my idea
of good defaults.  (note: I plan to steal this stuff from my project
logtool (http://www.xjack.org/logtool/), so if you're looking to contrib
to the effort, this is an area that's already covered as soon as I can 
get around to it :).

4.  Pending 3, setup snortconf to be able to give you a nice jump point
to kick over and view the syslog output in logtool.

5.  Write a nice little shell script for yee ole newbies that will do the 
following on an 'automagic' basis:

	a.  Download snort-current.tar.gz, unpack, and install in a 
	    "hands free" manner.  IE: user types "go", and everything
	    but writing snort.conf gets done for them automagically.

	b.  Ditto with snortconf.

	c.  Ditto with a few other useful-for-snort-users packages.  
END************************************************************************

6.  Perhaps get someone with some GTK/QT GUI coding skills to whip up GUI
versions of the menu's.  (no way am I ever tackling this aspect; I'm 
strictly a console guy :)

BEG************************************************************************
7.  Add option to generate a "startup/shutdown" script for Snort.  Probably
can borrow this from existing scripts and just have snortconf write-out
the existing scripts.  (remember, our goal is to make all the "background
work" transparent to the end user - so while this sounds silly from a geek
perspective, I think it would be good for yee ole end user).

8.  This should really be up at item 1, but lots of error checking of user
input to make sure they didn't enter bad data.
END************************************************************************

9.  Much much more to come, I have no doubt.

	-- A.L.Lambert <alambert@manisec.com>

