On 26/11/2012, at 18.09, John Horne <john.ho...@plymouth.ac.uk> wrote:
> On Tue, 2012-11-20 at 13:27 +0000, Bendtsen, Jon wrote: >> On 2011-11-11 12.22, John Horne wrote: >> >>> It is proposed that at the next release of rkhunter the '-r' >>> command-line option and the ROOTDIR config file option will be >>> deprecated. >>> >>> The code for these options has not really been maintained for quite some >>> time (past few years), and as such probably does not do what is >>> expected. The current code will be removed, and at some future time new >>> code written to provide similar options (once we have defined what the >>> options are and are not expected to do). >>> >>> If anyone is using either of these options in earnest, then please let >>> me know within the next few days. >> >> oh no :-( >> > Hello, > > The code never really worked that well. It was partially maintained > since we took over RKH, but it was obvious that the code did not do what > it should. As far as I could tell the code would never have really > worked unless you used two identical systems. This was not really much > use since it would be better to cater for systems of different release > versions (e.g. CentOS 5 and CentOS 6), or of completely different > systems (e.g. CentOS 6 and Solaris 10). Even the same systems would > cause warnings because of things like different versions of individual > packages (and hence file differences). Some things like the checks of > SSH settings, and perhaps hidden files may well have worked (although > even then differences between systems would cause a warning). It worked fine for me, but yes I did have a .conf file for each virtual guest and even in that .conf file I did have a TMPDIR, DBDIR and ROOTDIR which was set to unique values pr. virtual guest. In the beginning I got errors like what you described, but once I configured unique TMPDIR, DBDIR and ROOTDIR in the .conf file, I did not have any more trouble, even if I was checking different Linux distributions in different versions and even on a different architecture; arm, 32bit x86, AMD_64 > To rewrite the new code would take quite some time, and involve many new > options to the config file just to support this. I currently don't have > that time, and don't see it happening in the near future either. Sorry. I do not see what other options than unique DBDIR and TMPDIR would be needed. Would you care to elaborate which you think would be needed? JonB ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: INSIGHTS What's next for parallel hardware, programming and related areas? Interviews and blogs by thought leaders keep you ahead of the curve. http://goparallel.sourceforge.net _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
