Hello, I have recently added a section to the README file entitled 'Testing rkhunter without installing it'. It describes how it is possible to use the standalone installation to either test a CVS version of RKH, or, for new users, to try out RKH without having to fully install it. The standalone installation will not affect any other installed version of RKH on your system. As such it is ideal for performing tests of CVS versions of RKH. It is also very quick to install, test and then remove it completely :-)
I would suggest obtaining a copy of the current RKH CVS tarball (http://rkhunter.sourceforge.net/rkhunter-CVS.tar.gz), and extracting the README file. The new section contains details of the steps involved in installing RKH, and what they do. However, I suspect a lot of people would be happier if I simply list the commands that are required. They can then see whether they want to do this or not :-) The commands I typically use are these, but you may well need to modify them for your own system (e.g. if you use lynx rather than wget, etc). As root, type in: mkdir /tmp/rkh (this is the directory you are going cd /tmp/rkh to install RKH into) wget http://rkhunter.sourceforge.net/rkhunter-CVS.tar.gz tar xzf rkhunter-CVS.tar.gz (Solaris users may need to use gtar) cd rkhunter ./installer.sh --layout custom . --install (NOTE the dot (.) in there - this is the standalone installation) cd files That's it. Everything that RKH needs is now in the current directory. You can run RKH using './rkhunter', and use the '--update' and '--versioncheck' options if you want to. Any log file will also be created within this directory. The ONLY exception to this is if you use the '--debug' option, this will create the debug file in /tmp. So now you can run any tests you want to with the CVS version, but if you want to simply run a standard full check of your system then run: ./rkhunter --propupd --check --sk (This will first create the propupd.dat file in the directory, for the file properties tests, and then it runs the full check) You probably will get some warnings, but these will be from tests which you would normally whitelist (the passwd/group file tests always give a warning the first time they are run). If you want to whitelist things then just edit the './rkhunter.conf' file. Once you have finished all your tests, then simply delete the whole directory: cd /tmp /bin/rm -rf rkh That's it! Simple really. Now off you go and grab a copy of the CVS version and let us know if it works or not :-) Thanks, John. -- --------------------------------------------------------------- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287 E-mail: [EMAIL PROTECTED] Fax: +44 (0)1752 587001 ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
