> Do a 'ls -l all-2.0.tar.gz' and send us the results please, > as well as the md5 of the tar file you're getting.
Thank you for the quic response. For the last scheduled update (1:00 a.m. this morning), The directory created was: drwx------ 2 root root 4096 Sep 2 01:05 nessus-update-plugins-20505 And the files in the directory are: -rw------- 1 root root 1025 Sep 2 01:05 all-2.0.sig -rw------- 1 root root 3558561 Sep 2 01:05 all-2.0.tar.gz -rw------- 1 root root 56 Sep 2 01:00 all-2.0.tar.gz.md5 The file all-2.0.tar.gz.md5 contains: MD5 (all-2.0.tar.gz) = b9d6daad3c00f6d5a01df084b75c9e42 When I run md5sum on all-2.0.tar.gz myself, I get this: caa2abefa52659b7cd124a1a5c94419c all-2.0.tar.gz I scheduled a cron job to run nessus-update-plugins, this time with the -vv option, a few minutes ago. It worked. (No changes other than -vv versus -v. Your car never makes that funny noise for the mechanic, huh?). Here are the results: >From <snip>@<snip> Fri Sep 2 10:07:56 2005 Date: Fri, 2 Sep 2005 10:03:00 -0700 From: <snip>@<snip> (Cron Daemon) To: <snip>@<snip> Subject: Cron <snip>@<snip> /usr/local/sbin/nessus-update-plugins -vv X-Cron-Env: <SHELL=/bin/sh> X-Cron-Env: <HOME=/root> X-Cron-Env: <PATH=/usr/bin:/bin> X-Cron-Env: <LOGNAME=root> + '[' -z y ']' + tar=-xvf + '[' '!' -d /usr/local/lib/nessus/plugins ']' ++ pwd + cwd=/root + tmpdir= + test -z '' + tmpdir= + test -z '' + tmpdir=/tmp + mkdir -m 0700 /tmp/nessus-update-plugins-21585 + cd /tmp/nessus-update-plugins-21585 + /usr/local/bin/nessus-fetch --plugins-md5 + test -s /usr/local/lib/nessus/plugins/MD5 + '[' -x /usr/bin/diff ']' + diff /usr/local/lib/nessus/plugins/MD5 all-2.0.tar.gz.md5 + /usr/local/bin/nessus-fetch --plugins + test -x /usr/local/sbin/nessus-check-signature + /usr/local/sbin/nessus-check-signature all-2.0.tar.gz all-2.0.sig + rm -f all-2.0.sig + cd /usr/local/lib/nessus/plugins/ + /bin/gzip -cd /tmp/nessus-update-plugins-21585/all-2.0.tar.gz + tar -xvf - ./ ./04webserver.nasl ./12planet_chat_server_path_disclosure.nasl ./12planet_chat_server_plaintext_password.nasl ./12planet_chat_server_xss.nasl ./2bgal_sql_injection.nasl ... and on and on ... ./zyxel_http_pwd.nasl ./zyxel_pwd.nasl + rm -f /usr/local/lib/nessus/plugins/MD5 + mv /tmp/nessus-update-plugins-21585/all-2.0.tar.gz.md5 /usr/local/lib/nessus/p lugins/MD5 + cd /root + rm -rf /tmp/nessus-update-plugins-21585 + chown -R 0:0 /usr/local/lib/nessus/plugins/ + test -f /usr/local/var/nessus/nessusd.pid ++ cat /usr/local/var/nessus/nessusd.pid + pid=21535 + kill -1 21535 + exit 0 Regards, John Scherff -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Renaud Deraison Sent: Friday, September 02, 2005 8:56 AM To: [email protected] Subject: Re: Problem with nessus-update-plugins. On Sep 2, 2005, at 17:40, John Scherff wrote: > List, > > I run nessus-update-plugins via cron on four servers. For the past > several weeks, the update has failed every time with this error: > > all-2.0.sig is not the valid signature for all-2.0.tar.gz > > If I locate the directory and files nessus creates under /tmp (e.g., > /tmp/nessus-update-plugins-#####), I find all-2.0.sig, all-2.0.tar.gz, > and all-2.0.tar.gz.md5. If I run nessus-check- signature > all-2.0.tar.gz all-2.0.sig, I get the same error as above. Same thing > when I use the md5 signature file. Do a 'ls -l all-2.0.tar.gz' and send us the results please, as well as the md5 of the tar file you're getting. -- Renaud _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus _______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
