It's actually a bug in Inprotect itself and the website has a
workaround. By the way, while many of us Inprotect folk monitor the
Nessus list, it's probably better to direct questions about it to the
Inprotect list. You can sign up for it here
http://sourceforge.net/mail/?group_id=67220 .
Laters,
Dave King
http://www.thesecure.net
George Theall wrote:
On Tue, Nov 30, 2004 at 04:55:53PM +0100, Simon Meggle wrote:
I followed the installation manual of inprotect, but on step 12 (running
updateplugins.pl) i have big problems. After exectuting updateplugins.pl i
can see in the logfile:
...
Tue Nov 30 16:31:24 2004 updateplugins: No new plugins installed at
updateplugins.pl line 106.
...
Line 106 in updateplugins.pl is:
...
106==> system ("nessus-update-plugins.141 -u $inprotect_url/nessus") == 0
or die localtime(time)." updateplugins: No new plugins installed";
I don't use inprotect, but I wouldn't be surprised if the problem is the
same as what's been biting others recently -- nessus-update-plugins
fails to copy over the plugins if the list of plugins exceeds the amount
of space allocated by the kernel for command-line arguments. The
problem has been resolved in the latest version of Nessus.
You should be able to see if this is the issue by figuring out the exact
command being run in line 146 and running it by hand (minus any
commandline redirections) or alternatively just running
nessus-update-plugins as root.
George
------------------------------------------------------------------------
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
