On Fri, Aug 16, 2002 at 11:25:59 -0400, Michael Scheidell wrote: >> >> Hi all, >> >> I was able to reproduce the bad behavior with nessus-1.2.4 on >> FreeBSD-4.6-STABLE. With a patch based on the current revison 1.71 of >> nmap_wrapper.c the problem went away. >> >> I have now submitted an update of the FreeBSD-port. > > Can you have an official patch with a #ifndef BSD? > What is the need for that double signal alarm and why doesn't it cause > problems elsewhere? >
Theses two lines: signal(SIGALRM, SIG_IGN); alarm(0); only have the effect of ignoring the signal SIGALRM and resetting the timer for the SIGALRM signal. So doubling this makes no harm, but in fact is a noop. > what is the effect of taking it totally out of the 1.24 nessus ? I think: none. Best regards -- Udo Schweigert, Siemens AG | Voice : +49 89 636 42170 CT IC CERT, Siemens CERT | Fax : +49 89 636 41166 D-81730 Muenchen / Germany | email : [EMAIL PROTECTED] - [EMAIL PROTECTED]: general discussions about Nessus. * To unsubscribe, send a mail to [EMAIL PROTECTED] with "unsubscribe nessus" in the body.
