|
Well, don't know for Knoppix 2.6.12, but got 3.0.2 working without any
real problems under Knoppix 4.0.2 (running on a few machines) An overview of what I did (maybe missing some points as it has been a while now). Saved all my "data" from the nessus directories just in case. Removed the previous version with, to avoid conflicts (which will happen because previous versions probably have executables in your $PATH and the 3.0.2 version doesn't by default): apt-get remove nessus Installed the new version with (installed any prereqs it may have asked for, don't recall) dpkg --install Nessus-3.0.2-debian3_i386.deb Requested a new key and installed that. If you're behind a proxy first update first: /opt/nessus/etc/nessus/nessus-fetch.rc Activated key with /opt/nessus/bin/nessus-fetch --register yourkey Installed the client (this may ask for some prereqs): NessusClient-1.0.0.RC4 Note that this nessus installs in a different directory. For the different installs I've used so far: Databases are in: • /var/lib/nessus/users/ (apt-get installation) • /usr/local/var/nessus/users/ (nessus-install.sh installation) • /opt/nessus/var/nessus/users/ (dpkg –install Nessus-3.0.2 Default dir for server executables is: • /usr/sbin (apt-get installation) • /usr/local/sbin (nessus-install.sh installation) • /opt/nessus/sbin (dpkg –install Nessus-3.0.2) This dir contains: • nessus-adduser • nessus-check-signature • nessus-mkcert • nessus-rmuser • nessus-update-plugins • nessus-update-plugins-gpl • nessusd Default dir for client executables is (did not check this) • /usr/bin (apt-get installation) • /usr/local/bin (nessus-install.sh installation) • /opt/nessus/bin (dpkg –install Nessus-3.0.2) This dir contains: • nessus-fetch • nessus • nessus-build • nessus-fetch • nessus-mkcert-client • nessus-mkrand • startnessus Configuration is in: • /usr/local/etc/nessus (nessus-installer.sh) • /etc/nessus (apt install) • /opt/nessus/etc/nessus (dpkg –install Nessus-3.0.2) Note that with 3.0.2 the reports end up in you home directory (using the NessusClient). So even if you are user "tom" logging on to the nessus deamon with "scanner01" the scan results will end up in : /home/tom/.nessus This is inconvenient if you are sharing this scanner with a colleague. Note that the manual pages don't get linked for 3.0.2, as they are in /opt/nessus/man, you need to do this manually, or if you want to look up for example the man page on nessusd include the path with the man command: man -M /opt/nessus/man nessusd Note that the /opt/nessus/sbin and /opt/nessus/bin are not included in your path, so either type the full path , include these paths in your profile (probably /home/tom/.bash_profile or something), or link the files you want to use often, from /opt/nessus/bin to /usr/bin and /opt/nessus/sbin to /usr/sbin (whichever applies). George A. Theall wrote: On Mon, Jun 26, 2006 at 08:59:49AM -0700, Ron Backman wrote: |
_______________________________________________ Nessus mailing list [email protected] http://mail.nessus.org/mailman/listinfo/nessus
