Understood, and I am currently using the python script. I must have something wrong in my header/footer files because no matter what subset of plugins I choose, nessusd is overwriting the rc file with an rc file with virtually all except dangerous plugins enabled. If an rc file is corrupted or incorrect, is this the standard behavior for the daemon?
-- R. Brockway GCIH,GSEC,CCNA,CCDA,SCSA,SCNA,CCSE Network Security Specialist Ranum's Law - You can't solve social problems with software On Thu, 23 Mar 2006, George A. Theall wrote: > On Wed, Mar 22, 2006 at 01:23:52PM -0500, R. Brockway wrote: > > > I have noticed in 2.2.6 and 2.2.7 that if I run nessus from command line > > with a provided, already generated nessusrc file by -c that before nessusd > > starts that scan, my provided nessusrc file is replaced with a full > > nessusrc file auto-generated by nessus. > > This is how Nessus has always behaved - the file is rewritten when you > start a scan. > > > I had assumed that my custom nessusrc file (for example, only checking > > solaris local checks) might have problems, but they had been working fine > > in 2.2.5. > > Use one of the update-nessusrc scripts to maintain your rc file: > > http://www.tifaware.com/perl/update-nessusrc/ > http://www.edgeos.com/resources/ > > The first is a Perl script I wrote; the second is a Python script from > Edgeos Security. Both are free. > > George > -- > [EMAIL PROTECTED] > _______________________________________________ > Nessus mailing list > [email protected] > http://mail.nessus.org/mailman/listinfo/nessus > _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
