Re: Aha! snmp_portscan.nes lockups
Hugo van der Kooij <[email protected]>
| Newsgroups | gmane.comp.security.nessus.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 7 May 2004, Brian Costello wrote:
> It SEEMS like the problem is a combination of the timeout not killing the
> process, and a problem with the nessusd plugin code. To get this problem to
> happen, I just set the timeout value of the snmp_portscan plugin to 15
> seconds and kicked off a scan. About halfway through the third snmpwalk
> execution, the test timed out, and that was where the problem happened. As
> I mentioned before, sigterm_handler doesn't keep the latest snmpwalk child
> pid, it only keeps the pid from the version discovery execution. Therefore,
> this scan was unable to be killed.
....
> So, for a resolution, I can submit my suggested fix (context diff patch?)
> but I can't help thinking that there was a reason why the child pids were
> ignored. I'll wait to see what other people say prior to submitting any
> code.
Did you submit the code somewhere? I hit the same issue but without the
coding skills to get this far into analyzing and fixing it.
Hugo.
--
All email sent to me is bound to the rules described on my homepage.
[email protected] http://hvdkooij.xs4all.nl/
Don't meddle in the affairs of sysadmins,
for they are subtle and quick to anger.
_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel