Re: How to start exporting Nessus results to a DB

Javier Fernandez-Sanguino wrote:
> Eric Arnoth wrote:
> 
>> ACK!  I hit send a bit too early on this, I wasn't quite 
>> finished...I'm currently looking at the functions in save_mysql.h, 
>> trying to figure out how well that accomodates transactions...sorry 
>> for the premature send!  
> 
> 
> 
> Oh. Please check save_db.{h,c} best. save_mysql has been superceeded by it.
> 
> Javi
> 

Re-reading my mail I believe it might not be understood properly. I 
meant that the code in save_mysql.c which was previously called from 
nessusd.c/attack.c directly is now called through an abstraction layer 
that is coded in save_db.c so really:

nessusd.c --\                      --- save_mysq.{h,c} (only one atm)
              ---> save_db.{h,c} ---|
attack.c  --/                      |-- save_pg.{h,c} (planned)
                                    |
                                    |-- save_oracle.{h,c} (expected :-)
                                    |
                                    |.....

So depending on what you ./configure you will enable/disable either one 
of the database backends (you will probably be able to even have more 
than one backend).

Regards

Javi