Re: mySQL database for nessusd (code!)

Eric Arnoth <[email protected]>
Newsgroups gmane.comp.security.nessus.devel
Message-ID <[email protected]>
Could you post to the list which database scheme you're using?  I got lost in 
all the threads, my inbox is overflowing from neglect because of the time I 
spent on the SQL worm last week, so I'm not sure what the final cut was.

I'm wondering if both PostgreSQL and MySQL could be supported.  Perhaps 
abstracting the database transaction layer?  I apologize if this is digging 
up something that was already settled.

Also, has any decision been made with regards to using transactions?  Since a 
single scanner might be running multiple scans for multiple clients, it might 
be a good idea to make use of. 

-- 
Eric I. Arnoth    CISSP (http://www.isc2.org)        
[email protected]                
http://mywebpages.comcast.net/earnoth
¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø¤ø,¸¸,ø¤º°*°º¤ø,¸¸,ø


On Thursday 06 February 2003 15:21, William Heinbockel wrote:
> On Thu, 6 Feb 2003, Minderhout, Doug wrote:
> > I am interested in contributing whatever I can to this. There are
> > probably going to be some tough decisions to be made in the process
> > of moving nessus over to a database backend.
> >
> > I'll snag a copy of your code and start looking through it tonight.
> > I think Renaud actually gave Javi some hints in a previous email.
> > I need to go back and look for that.
>
> Currently, I'm developing just a library of commands to be integrated into
> nessusd.  I just started learning mySQL on Tues ;) so I'm not familiar
> with it in any way.  Also, the aim of the project is not to replace the
> existing datastructures in Nessus.  It is being developed in addition to
> so that large amounts of scan data can be easily stored and admin can
> easily draw out information and perform trend analysis.
>
> Renaud's suggestions from before where more target to use the database
> in the same fashion as the knowledge base - to store the RESULT of the
> scans.  Javi and myself agree, it would be better to get realtime
> information from Nessus.
>
> The code that I have is relatively simplistic... it pretty much
> translates method calls into mySQL commands.  Right now, I am figuring
> out if the information in the database is easily obtainable, and
> where the best place would be to save the information to the database.
>
> > -----Original Message-----
> > From: William Heinbockel [mailto:[email protected]]
> > Sent: Thursday, February 06, 2003 12:23 PM
> > To: [email protected]
> > Subject: mySQL database for nessusd (code!)
> >
> >
> > Just an update on the database backend for nessusd...
> >
> > I've started coding a mysql interface/library for nessusd.
> > It is written in C and uses mysql.h (the mysql C API).
> >
> > The code can be found at:
> > <a href="http://www.rit.edu/~wjh3710/pub/save_mysql.c">save_mysql.c</a>
> > and
> > <a href="http://www.rit.edu/~wjh3710/pub/save_mysql.h">save_mysql.h</a>
> >
> > This is by no means complete. I will try to update it as much as
> > possible. But if others want to assist with the development, it
> > might be best to set up a CVS server (anyone interested?).
> >
> > I'm working with the database schema that Javi posted awhile back,
> > but due to my lack of SQL knowledge and the way nessusd is set-up,
> > I don't think that some of the tables can be setup in that manner.
> >
> > I think the easiest way to incorporate the non-session specific data
> > (i.e. the Nessus-plugin table and Services table and the like...) is
> > to write a simple [perl?] script to create an sql modules directly
> > from the plugins' directory and hard code a script to deal with the
> > services.
> >
> > ----------------------
> > William Heinbockel
> > Information Security Incident Response Assistant
> > Co-op Risk & Safety Management
> > Rochester Institute of Technology
> > E-mail: [email protected]
>
> ----------------------
> William Heinbockel
> Information Security Incident Response Assistant
> Co-op Risk & Safety Management
> Rochester Institute of Technology
> E-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.