I slimmed down the distributed nessus-update-plugins to suit my local needs, and give a diff output. Works well enough although I'm sure it could be refined.
Run from a cron job it'll give you a list of the new plugins. ------------------ #!/bin/sh cwd=`pwd` mkdir "/tmp/nessus-update-plugins-$$" cd "/tmp/nessus-update-plugins-$$" /usr/local/bin/lynx -source http://www.nessus.org/nasl/all-1.2.tar.gz | tar xvzf - > /root/.plugins.new diff /root/.plugins.new /root/.plugins cp /root/.plugins.new /root/.plugins cp *.nasl /usr/local/lib/nessus/plugins/ cp *.inc /usr/local/lib/nessus/plugins/ cd "$cwd" rm -rf "/tmp/nessus-update-plugins-$$" chown 0 /usr/local/lib/nessus/plugins/*.nasl chgrp 0 /usr/local/lib/nessus/plugins/*.nasl test -f /usr/local/var/nessus/nessusd.pid && ( pid=`cat /usr/local/var/nessus/nessusd.pid` kill -1 $pid 2>/dev/null ) ------------------------- ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, August 08, 2002 3:05 AM Subject: automatic update > Hello > > What is the best way to verify that the command > nessus-update-plugins has actually added all the recent > plugins? > > The command seems to run fine with no error message, but > I would feel better if I could actually check that the latest scripts > have been added. > > Thanks > > Gary > > - > [EMAIL PROTECTED]: general discussions about Nessus. > * To unsubscribe, send a mail to [EMAIL PROTECTED] with > "unsubscribe nessus" in the body. > - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
