Nessus 3.0

[macamba]

If i enter the command $PATH i see that /opt/nessus/bin and /opt/nessus/sbin are in there. If i edit /etc/profile is see the following text:

---------------------------------------------
# Set the default system $PATH:
PATH="/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/usr/lib/java/bin:/opt/nessus/bin:/opt/nessus/sbin:/pentest/forensics/sleuthkit/bin"
---------------------------------------------

So the paths should be alright in my case. My point that i don't know sure whether 2.2.6 is running now or 3.0.1.

I tested the following:
- /opt/nessus/sbin/nessusd -d
- /etc/rc.d/init.d/nessusd -d

Bought gives the following output:
-------------------------------------------------
This is Nessus 2.2.6 for Linux 2.6.12.2
compiled with gcc version 3.3.5
Current setup :
nasl : 2.2.6
libnessus : 2.2.6
SSL support : enabled
SSL is used for client / server communication
Running as euid : 0
-------------------------------------------------

I think the output of "/opt/nessus/sbin/nessusd -d" should be version 3.0.1?

How do i check now which version is running

[macamba]

Created by: Macamba
Date: 5 march 2006

For this installation procedure to work
- Back|Track needs to be installed on harddisk;
- you should login as root.

Step 1:
Download the following packeges from Nessus.org to /tmp on your harddisk:
- Nessus-3.0.1-fc4.i386.rpm (server)
- NessusClient-1.0.0.RC4.tar (client)

Step 2: remove Nessus 2.2.6
- cd /usr/local/sbin
- ./uninstall-nessus (remove everything)

Step 3: Install Nessus 3.0.1
Convert the server packege to .tgz with the following command:
- cd /tmp
- rpm2tgz Nessus-3.0.1-fc4.i386.rpm (now you have Nessus-3.0.1-fc4.i386.tgz in /tmp)
- pkginstall Nessus-3.0.1-fc4.i386.tgz (or use pkgtool command to select the package)

Step 4: Install Nessus 1.0 0 RC4
- cd /tmp
- tar -zxf /tmp/NessusClient-1.0.0.RC4.tar.gz
- cd NessusClient-1.0.0.RC4/
- ./configure
- make
- make install (the following message appears " NessusClient has been sucessfully installed")

Step 5: Configure Nessus
- check with the $PATH command if "/opt/nessus/bin" and "/opt/nessus/sbin" are configured
- if not, add "/opt/nessus/bin" and "/opt/nessus/sbin" in "/etc/profile"
--------------------------------------------------------------------------------------
# Set the default system $PATH:
PATH="/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/usr/games:/usr/lib/java/bin:/opt/nessus/bin:/opt/nessus/sbin:/pentest/forensics/sleuthkit/bin"
--------------------------------------------------------------------------------------
- copy all libraries from "/opt/nessus/lib/" to "/lib"
- cd /lib
- ln libdb-4.2.so libdb-4.3.so
- edit "/etc/ld.so.conf" and add the following path: "/opt/nessus/lib/
- cd /etc/rc.d
- ldconfig
- cd /opt/nessus/sbin
- nessus-mkcert
CA certificate life time in days [1460]: 1460
Server certificate life time in days [365]: 365
- nessus-adduser
Login : root
Authentication (pass/cert) [pass] : pass
Login password : toor
Login password (again) : toor
- the following message appears: "Enter the rules for this user, and hit ctrl-D once you are done : (the user can have an empty rules set)"
- ctrl-D
- Is that ok ? (y/n) [y] y

Step 6: Run Nessus
- nessusd
- NessusClient

[armedpilot]

Most commands, support man pages, and also have a command line help option, such as "nessusd --help". "nessusd -v" will tell you which version the executable is. The 3.0.1 version should indicate 3.0.1.

I think the output of "/opt/nessus/sbin/nessusd -d" should be version 3.0.1?

How do i check now which version is running

[imported_spaceghost]

Do the BackTrack Nessus scripts still work with Nessus 3.0?

[imported_spaceghost]

The scripts seem to work but Nessus itself doesn't seem to work for me unfortunately.

[macamba]

What error do you get?

[imported_spaceghost]

I started over and now nessusd works correctly. Before it wasn't scanning targets. It would say all the targets are dead and the nessus.dump file had something like iface_get(eth0) failed.
The only other problem I have now is this:
http://mail.nessus.org/pipermail/nes.../msg00124.html
When I use the nessus client (both RC1 and RC4) and I switch the Trused CA option in the GUI to use /opt/nessus/com/nessus/CA/cacert.pem instead of /usr/local/com/nessus/CA/cacert.pem then I don't get the errors anymore.

[imported_relik]

I followed these steps to the dot, when I use nessus-fetch or nessus-fetch with my register ID I get

nessus-fetch: error while loading shared libraries: libnessus.so.2: cannot open shared object file: No such file or directory.

Anyone running into this same problem?

[imported_relik]

Did it by using the full path /opt/nessus/bin/nessus-fetch --register etc.

[phpandromeda]

i followed the things that i saw on this page to insall nessus
but when i tried to execute nessus -d
the system says

BT sbin # nessusd
Floating point exception