On Fri, 2009-10-30 at 12:43 -0600, Mike McCarty wrote: > Sportsman wrote: > > Hello all, just thought I'd let the users know that I was able to resolve > > the PermitRootLogin issues that I was experiencing with some valuable > > guidance from John and Unspawn. It seems that I have two rkhunter.conf > > files on my server. One is under /usr/local/etc/rkhunter.conf and the other > > (right one) is under /etc/rkhunter.conf. As soon as I made the changes to > > the /etc/rkhunter.conf file everything worked as it should. Not sure why > > there are two of the files as the one I was making changes to didn't do > > anything. I'd be curious to know if everyone has two rkhunter.conf files on > > their system to make sure it is normal and that something didn't get messed > > up during the initial install of Root Hunter. Anyway, thanks again to all > > for your help and guidance. Much appreciated. > > I thought that was part of the installation. The install puts an > "example" in the install directory, and one is intended to copy it > to /etc/rkhunter.conf and edit it appropriately. > Hmm, not really. At installation you specify where to install the files by using the 'layout' option. By default this will use /etc to hold the RKH config file (rkhunter.conf). However, if you tell the installer to put the files into /usr/local then the config file will be in /usr/local/etc and RKH will expect it to be there and not in /etc. Using the installer '--show' option will show you where the installer will put the files.
RKH will only use one configuration file. However, it is perfectly possible to have more than one config file on a system if a previous installation of RKH - perhaps an older version of RKH - put the files in a (now) non-default location. E.g, installing RKH 1.2.9 might have put the config file into /usr/local/etc, and then installing RKH 1.3.4 by default will put the file into /etc. Needless to say it is recommended to keep the files in the same place each time RKH is installed. If not, then ensure that the old version is removed completely. The installer has a '--remove' option. Next release will make things a bit easier as it allows you to create a 'local' config file. You then make any configuration changes to the local file, and not the installed rkhunter.conf. When upgrading to further RKH versions (1.3.8 etc onwards) you can tell the installer to overwrite the default installed config file as well (at the moment it installs it with a number appended to its name (e.g. rkhunter.conf.1054), which then has to be copied into place). This makes future installations easier since your local config file is untouched, and you don't need to copy/move the installed config file anywhere. This is all in the current CVS version (1.3.5). John. -- John Horne, University of Plymouth, UK Tel: +44 (0)1752 587287 Fax: +44 (0)1752 587001 ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
