Thanks for the response Al. I took on the maintenance job without knowing about these version differences in the infrastructure and don't know much about RKHunter. The docs aren't very well documented (or that I can't find them properly) so I can't tell what has been changed between any version.
And no, I don't actually have a "/path/to/exclude/bla/bla". That's just silly. The actual path is more like "/opt/com/apps/bin/connect/". Anyways, the path is actual and exists but I doubt that's relevant at this point. I'll try to convince the clients to upgrade RKHunter to the latest version. On Wed, Mar 6, 2019 at 5:09 PM Al Varnell via Rkhunter-users < rkhunter-users@lists.sourceforge.net> wrote: > My first reaction is why would you use anything older than version 1.4.6 > which is the current supported version with many bug fixes and looks for > current rootkits? Those two versions are five and seven years old now and > probably won't find any RK's in use today. > > So you actually have a “/path/to/exclude/bla/bla” that needs to be > excluded? There is nothing like that in the current /etc/rkhunter.conf, so > unless you have a actual path named that, delete the entry. > > Sent from my iPad > > -Al- > > > On Mar 5, 2019, at 20:39, Abdul Qoyyuum <aqoyy...@cardaccess.com.au> > wrote: > > > > Hello fellow sysadmins, > > > > New to the mailing list. A system infrastructure that I'm maintaining > has a problem with RKHunter. Even more so that the RKHunter version is not > the same across all virtual machines. Some are on 1.4.0 and some are on > 1.4.2. When `rkhunter --propupd` is ran by puppet, this shows up in the > logs: > > > > Invalid USER_FILEPROP_FILES_DIRS configuration option: Relative > pathname: !/path/to/exclude/bla/bla > > > > In correspondence to my /etc/rkhunter.conf: > > > > USER_FILEPROP_FILES_DIRS="!/path/to/exclude/bla/bla" > > > > This is only affected on RKHunter version 1.4.2 and above. The thought > of downgrading to make this work is silly and I can't find anything in the > docs/wiki for making this work for the later version. On another hand, > commenting out that config line and running `rkhunter --propupd` again did > make it pass but it look longer than expected to complete as opposed to the > RKHunter version 1.4.0 environments. > > > > Any help is appreciated thanks. > > -- > > Abdul Qoyyuum Bin Haji Abdul Kadir > > HP No: +673 720 8043 > > _______________________________________________ > > Rkhunter-users mailing list > > Rkhunter-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/rkhunter-users > > > > _______________________________________________ > Rkhunter-users mailing list > Rkhunter-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/rkhunter-users > -- Abdul Qoyyuum Bin Haji Abdul Kadir HP No: +673 720 8043
_______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
