Re: [Inprotect-devel] New pre-cvs code

[Greg K. <gr...@no...>]

UPDATE: I have completed a set of changes to make Inprotect work with 
Nessus 2.2.x, and in fact with any future version of Nessus as long as 
there are no major changes to the nessus client command line output.

The new code is sitting at http://inprotect-devel.ana.no1.com.au/

Things to do to upgrade:

Before starting anything, upgrade to nessus 2.2.x

1. You will need to make some SQL changes to your indexes. I did my 
changes through a cute "gui" interface. If I knew what the equivalent 
SQL code was, I would paste it in a document to help you.... If someone 
can tell me what the SQL code is, I'd love to hear from you. The code 
needs to do the following:
(A) nessus_preferences: make nessus_id the primary key, and allow 
duplicate values in the old id field.
(B) nessus_settings_preferences: remove the not null constraint on the 
id field

2. run the new "updateprefs.pl" file. This will suck down information 
from the Nessus server into the inprotect database about all the 
parameters that the server and the plugins can support. It will 
automatically check for and create a new table if required. You should 
also run updateplugins.pl to get any new nessus 2.2.x plugins into your 
database.

3. defaults.php and settings.php - Copy these to your web server directory.

4. Login to inprotect, Go to settings, Nessus scan profiles, Edit 
default profile. The new screen will look a little different. It is 
IMPORTANT that you SAVE data on this screen, even if you make no 
changes. This will allow default values for the new parameters to be 
written to your existing inprotect database. If you fail to do this 
step, you will not be able to edit these values under other custom profiles.

5. Go to Go to settings, Nessus scan profiles, and edit your profiles. 
The screen should look almost exactly like the default profile. I 
recommend re-saving all of your existing profiles. If you dont, the new 
items will be omitted from the nessus config file, and I cannot 
guarantee how nessus will behave for un-defined values.

6. Test. Report bugs. Have fun, and happy scanning!