Yes, that helps. I reckon the corresponding place in the 2.0.8a source is at around line 270 in attack.c which should sleep for however long you specify when it's about to launch a plugin. Haven't tested yet since my development environment is on the wrong end of a dead 2Mbit link :-( When I can get to a machine that I can compile on, I'll report on its success/failure.
Thanks. -----Original Message----- From: George Theall [mailto:[EMAIL PROTECTED] Sent: 08 January 2004 16:28 To: [EMAIL PROTECTED] Subject: Re: Finding the plugin that causes a loop? On Thu, Jan 08, 2004 at 10:32:59AM -0000, Hemsley, Trevor wrote: > I have to discover which of the 220 or so tests that > I have configured is causing this. I thought I could do this by setting > 'delay_between_tests = 120' or something like that so that only one test > every two minutes would be launched. ... > Unfortunately, it appears that this parameter doesn't do what it suggests No, it affects the delay between two consequetive attacks on the *same* port, but only in Nessus 1.x. > Does anyone have any alternative debugging methods I can use instead > of this? In <http://list.nessus.org/nessus/0303/5373.html>, Renaud advises modifying the source, adding a sleep, and recompiling. George -- [EMAIL PROTECTED] _______________________________________________ Nessus mailing list [EMAIL PROTECTED] http://mail.nessus.org/mailman/listinfo/nessus
