On Sun, Feb 29, 2004 at 09:13:30PM +0100, Pavel Kankovsky wrote:
> On Thu, 26 Feb 2004, Renaud Deraison wrote:
>
> > We _should_ but I've been lazy. And in anyway, this does not really
> > matter- the parent process is subject to the nessusrc plugin timeout,
> > and if it dies it will kill the son.
>
> 1. the timeout in "nessus.rc" can be longer than 120 s
> 2. the timeout should (IMHO) limit the time Nessus spends running a
> particular test against one port, not the total time against *all*
> ports where a particular service has been found (*)
Yeah, I was thinking the other way - ie: I don't want a plugin to stall
the whole scan.
I've fixed that in CVS yesterday - the timeout is set to the one defined
in nessusd.conf. I won't increase the total timeout anyway - plugins
taking that much time need to be fixed. With over 2000 plugins, it's not
acceptable to have one plugin lasting 120 secs anyway, except for very
special cases (ie: find_services, and even though, that's too long).
-- Renaud
_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus
