On Thu, Aug 15, 2002 at 15:05:01 -0400, Michael Scheidell wrote:
>> "Benninghoff, John" <[EMAIL PROTECTED]> writes:
>> 
> >> I should add that this problem exists in nessus 1.2.4.
>> 
>> Try to update nessus-libraries/libnessus/network.c from CVS or apply
>> this patch. I'm not sure it is enough but I do not want to commit all
>> my modifications...
>> 
> 
> I didn't check thr rcs files, but did delete the nmap_wrapper.c and do a
> cvs just now.  did a clean and recompile, it looks like nmap works now.
> 

Hi all,

I was able to reproduce the bad behaviour 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.

Attached is the patch against 1.71, which deletes doubled signal/alarm-pairs
and double "#ifdef FAKE_PROGRESS_BAR" lines.

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]

Index: nmap_wrapper.c
===================================================================
RCS file: /usr/local/cvs/nessus-plugins/plugins/nmap_wrapper/nmap_wrapper.c,v
retrieving revision 1.71
diff -u -r1.71 nmap_wrapper.c
--- nmap_wrapper.c      15 Aug 2002 12:56:58 -0000      1.71
+++ nmap_wrapper.c      16 Aug 2002 14:55:02 -0000
@@ -195,10 +195,6 @@
  signal(SIGALRM, SIG_IGN);
  alarm(0);
 #endif
-#ifdef FAKE_PROGRESS_BAR
- signal(SIGALRM, SIG_IGN);
- alarm(0);
-#endif
  kill_nmap();
  exit(0);
 }
@@ -616,16 +612,12 @@
  Hostinfos = hostinfos;
  
 #ifdef FAKE_PROGRESS_BAR
-#ifdef FAKE_PROGRESS_BAR
  signal(SIGALRM, SIG_IGN);
  alarm(0);
-#endif
  signal(SIGALRM, update_progress_bar);
  alarm(1);
 #endif
  fp = ptycall_nmap (desc, NMAP, argv, &nmap_pid);
-#ifdef FAKE_PROGRESS_BAR
-#endif
  destroy_argv (argv);
  }
 
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.

Reply via email to