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.
When I run
nessus-update-plugins -v from the command line, it seems to
have no problems.
Does
nessus-update-plugins have a problem with cron?
Is there something missing from cron's environment that might be causing this
problem?
No useful google
hits on this one (a few others are having the problem, but no solutions
offered). I wonder if this is more widespread, but people just aren't
reading the cron output in their mailboxes.
Any assistance
appreciated.
John
Scherff
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
