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
