All I did was upgrade rkhunter? Why should I need to whitelist any files if they were fine before?
John Horne wrote: > On Wed, 2007-08-08 at 01:05 -0700, Johnny Stork wrote: > >> I just upgraded to 1.30 on a couple of RHEL 4systems but I get a full >> list of no hashes found. So I downloaded the hashupd.sh script, ran it >> >> > RKH 1.3.0 does not use the hashupd.sh script or the os.dat file. Forget > about them. Suggest you look in the log file to see why you have been > given warnings. Then look in the rkhunter.conf file to see if the > entries can be whitelisted (assuming they are valid). > > > > John. > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Rkhunter-users mailing list Rkhunter-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rkhunter-users
