George- Genius!
This is exactly what I'm looking for. I was able to download and modify your script and produce the results that management wanted. All I have to do is throw this puppy into a cron and i'm good to go. I do have a question... pertaining to plugin updates, would you recommend the solution be to disable the plugin options in /opt/nessus/etc/nessus/nessusd.conf file? More specifically the following options: # Automatic plugins updates - if enabled and Nessus is registered, then fetch the newest plugins from plugins.nessus.org automatically auto_update = yes # Number of hours to wait between two updates auto_update_delay = 24 # Should we purge the plugin db at each update ? (slower) purge_plugin_db = no I was thinking that this was the best, and then just have the script manipulate and handle the plugins. Let me know your thoughts. Thanks ashby On Wed, Nov 19, 2008 at 1:04 PM, christopher ashby <[EMAIL PROTECTED]> wrote: > George- > > Thanks for the heads up, I believe that this is what i am looking for. > I'm going to download and play around, if something comes of it I > will let you know. > > Thanks again > > ashby > > > > On Mon, Nov 17, 2008 at 3:01 PM, George A. Theall > <[EMAIL PROTECTED]> wrote: >> On Nov 17, 2008, at 9:05 AM, christopher ashby wrote: >> >>> Was just wondering how everyone manages there plug-in subscriptions, >>> more specifically what plug-ins were updated, added, and or removed >>> (if applicable). I would like to receive a daily report either >>> automatically created which would inform me of all the updates that >>> have been applied to existing plug-ins, and any new ones that have >>> been downloaded from the repo. >> >> Several years ago I developed a Perl script that you might be >> interested in. It's not a Tenable product, though. And it requires a >> bit of setup, although nothing that a reasonably good sysadmin or >> Perl programmer should have difficulty with. The script is called >> update-nessus-plugins, and works as a wrapper around the script nessus- >> update-plugins that's included with Nessus. It offers options for >> backing up the plugins tarball prior to running an update as well as >> summarizing changes in the plugins, as context diffs when possible. >> The script is free and should run on most any sort of *nix system. You >> will need another of my scripts (describe-nessus-plugin) and to >> configure plugin updates to operate through cron rather than the >> Nessus server directly. For more info, look at >> http://www.tifaware.com/perl/update-nessus-plugins/ >> . >> >> 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
