On Mon, May 31, 2004 at 11:55:58AM +0200, Hugo van der Kooij wrote:
> On Mon, 31 May 2004, Axel Thimm wrote:
> 
> > On Thu, May 27, 2004 at 07:08:43PM +0000, [EMAIL PROTECTED] wrote:
> > > Just getting ready to try install with
> > >
> > > RedHat Enterprise ES v3 (yes I bought it)
> > > and
> > > Fedora Project 2
> > >
> > > Any gotcha's that anyone has seen with either?
> >
> > For FC2 there are rpms at http://ATrpms.net/name/nessus/. RHEL builds
> > may follow soon, but you can grab src.rpm and spec files to build from
> > these.
> 
> Just added it to the FAQ.

Thanks!

> But do these work well? I have tried the FC1 packages but they resulted in
> unpredictable segmentation faults.

I am using FC1 builds since quite some time. Could you check with rpm
-V, if perhaps something has broken? Make sure that you have no mixing
of /usr and /usr/local components, in case you have a local build
there. ldd on the segfaulting binary should display which libraries
are used, for example (in doubt you can temporarily rename /usr/local
to get it out of the LD path):

# ldd `which nessusd`
        libnasl.so.2 => /usr/lib/libnasl.so.2 (0x00101000)
        libnessus.so.2 => /usr/lib/libnessus.so.2 (0x00920000)
        libhosts_gatherer.so.2 => /usr/lib/libhosts_gatherer.so.2
        (0x008d7000)
        libpcap-nessus.so.2 => /usr/lib/libpcap-nessus.so.2
        (0x008de000)
        libutil.so.1 => /lib/libutil.so.1 (0x00de6000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00c48000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x0090c000)
        libssl.so.4 => /lib/libssl.so.4 (0x065bb000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x06e5e000)
        libdl.so.2 => /lib/libdl.so.2 (0x007cf000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00cd9000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00d42000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cd4000)
        libwrap.so.0 => /usr/lib/libwrap.so.0 (0x00a12000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00670000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2
        (0x00dd1000)
        libz.so.1 => /usr/lib/libz.so.1 (0x008c4000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00658000)

# ldd `which nessus`
        libnessus.so.2 => /usr/lib/libnessus.so.2 (0x00920000)
        libhosts_gatherer.so.2 => /usr/lib/libhosts_gatherer.so.2
        (0x008d7000)
        libpcap-nessus.so.2 => /usr/lib/libpcap-nessus.so.2
        (0x008de000)
        libutil.so.1 => /lib/libutil.so.1 (0x00de6000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x00c48000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x0090c000)
        libssl.so.4 => /lib/libssl.so.4 (0x065bb000)
        libcrypto.so.4 => /lib/libcrypto.so.4 (0x06e5e000)
        libdl.so.2 => /lib/libdl.so.2 (0x007cf000)
        libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0x00cd9000)
        libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0x00d42000)
        libcom_err.so.2 => /lib/libcom_err.so.2 (0x00cd4000)
        libgtk-1.2.so.0 => /usr/lib/libgtk-1.2.so.0 (0x00276000)
        libgdk-1.2.so.0 => /usr/lib/libgdk-1.2.so.0 (0x003de000)
        libgmodule-1.2.so.0 => /usr/lib/libgmodule-1.2.so.0
        (0x00a08000)
        libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x0018c000)
        libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x00b4b000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x008b4000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x007d4000)
        libm.so.6 => /lib/tls/libm.so.6 (0x007ab000)
        libc.so.6 => /lib/tls/libc.so.6 (0x00670000)
        libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2
        (0x00dd1000)
        libz.so.1 => /usr/lib/libz.so.1 (0x008c4000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00658000)

> Building from original souces however works quite well. (Except the
> known issue which hits you if you run snmp_port_scan.)
-- 
Axel.Thimm at ATrpms.net

Attachment: pgprF70HUuyYR.pgp
Description: PGP signature

_______________________________________________
Nessus mailing list
[EMAIL PROTECTED]
http://mail.nessus.org/mailman/listinfo/nessus

Reply via email to