Re: nessus and AMD64 again

On Jan 8, 2004, at 5:00 PM, Gene C. wrote:

> In my attempts to get nessus running (at least building for now) as a 
> 64 bit
> application, I have hit a problem.
>

> 3.  The problem is that the libpcap libraries are installed into 
> /usr/lib
> rather than /usr/lib64.  Per convention, /usr/lib is reserved for 32 
> bit
> libraries on dual (32/64 bit systems) and 64 bit libraries are placed 
> in
> /usr/lib64.  The other libraries involved in nessus-libraries are 
> properly
> installed into /usr/lib64.

You're probably right in your fix (using $libdir should solve the 
issue). I'll
comming a CVS right away.

>
> 4.  Is there some reason that nessus needs its own version of libpcap? 
>  Are
> there some unique modifications that have been made to libpcap that 
> are not
> part of libpcap 0.7.2?  Couldn't nessus simply use the regular libpcap 
> and,
> at least on linux (or specifically Red Hat/Fedora) systems, not 
> install its
> unique libpcap?

I have had numerous issues with libpcap 0.7.x on Linux. It seems that 
they try
to use the bpf-like architecture offered by the kernel, but libpcap 
0.7.x hates to
have too many pcap descriptors open at the same time. The solution 
would be
to use the userland pcap workaround I use for BSD systems now that it's 
been
extensively tested.  Also I'd need to make sure that pcap 0.7.x is 
non-blocking
on Linux (the older "stock" pcap libraries were blocking - ie: 
pcap_read() would
not return until a packet hits the filter).

So all in all, I'd love to get rid of libpcap-nessus, but that's not 
necessarily as easy
as it sounds.

						-- Renaud

_______________________________________________
Nessus-devel mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus-devel