Hi,
Forgive the slightly off-topic post, but I was wondering if someone
would be willing to talk about threads and pcap, perhaps off list?  I
noticed nessus seems to be using both.  My first impression was nessus
was using a certain number of worker threads, one per host being
scanned. 

I've been looking at libpcap, and it appears it's not completely
thread safe (for example, forking off 100 threads and calling
pcap_compile will segfault about half the time w/ latest libpcap on
linux...I haven't tracked down why yet but the use of static buffers
throughout the library is my first idea of the culprit).  How does
nessus deal with pcap so that it's safe, yet efficient?

I was, for a separate application, planning on creating a thread and
pcap_t for each host (with filter set accordingly) being processed,
but that doesn't appear to be safe.

Thanks,
david
-
[EMAIL PROTECTED]: general discussions about Nessus.
* To unsubscribe, send a mail to [EMAIL PROTECTED] with
"unsubscribe nessus" in the body.

Reply via email to