Re: New NESSUS_SQL tag in CVS sources

William Heinbockel wrote:

> I was just looking over the database schema(.png) in the CVS there
> are a couple of things that I suggest changing.
> 
> I don't see any use for the Knowledgebase table.

The knowledgebase items that are currently stored in text files could be 
stored in the database. I.e. plugins could add them there too (includes 
information such as OS of the remote host)

> HOST Table:
>   Change the IP to VARCHAR(16), unless you want to add it '0' fillers

You are right.

>   Add StartTime and EndTime values
>   Add a Status value - DEAD, CURRENTLY TESTING, or SUCCESS (or similar)

Yes, those are good suggestions.

> 
> EXECUTED_PLUGINS Table:
>   Change the Complete value to be of TinyInt (or similar) so that the
>     status can be more than two options - VULNERABILITY FOUND,
>     TEST PASSED, PLUGIN NOT RUN (failed a dependency)
> 
> Would there be any benefit to adding CVE and BID numbers into the
> NESSUS_PLUGIN Table?

Not really, I believe it ties us too much since there are some plugins 
that are related to two or more CVE and/or BID items.

> Also, some of the Fields will have to support NULL values.

If there's a NOT NULL you do not force to add any information in the 
column IIRC.

> 
> Currently, I am upgrading my files to match the schema.
> Also, I have renamed the save_mysql files to save_db and made the
> code inside Nessus as well as the code in the database library, more
> flexible so that other db architectures can easily be added.
> 
> I will hopefully upload the files to Javi in the next couple of days
> so that he can add them into the CVS repository.


Great, I have added the save_mysql.c code and the patches for the 
moment. Feel free to send any code my way :-) Adding information in the 
configure to detect database libraries is in my TODO.

Javi

PS: I'm adding all your suggestions to the TODO since Eric is going to 
give me a .dia that does not segfault on me ;-)