Bug 344531

Summary:	rkhunter: check failure
Product:	[openSUSE] openSUSE 10.3	Reporter:	Klaus Singvogel <kssingvo>
Component:	Security	Assignee:	Lars Vogdt <lars.vogdt>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	lars.vogdt, security-team
Version:	Final
Target Milestone:	---
Hardware:	All
OS:	openSUSE 10.3
Whiteboard:
Found By:	Development	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Klaus Singvogel 2007-11-28 09:08:13 UTC

Running rkhunter daily per crontab shows the following error:

---------------------------------------------------------------------------
+ /sbin/checkproc /etc/cron.daily/suse.de-rkhunter
+ test -x /etc/cron.daily/suse.de-rkhunter
++ /usr/bin/basename /etc/cron.daily/suse.de-rkhunter
+ BASESCRIPT=suse.de-rkhunter
+ nice -n 15 /etc/cron.daily/suse.de-rkhunter
+ local ERRNO=1
+ '[' 0 -eq 1 ']'
+ echo 'suse.de-rkhunter returned 1'
+ /bin/logger -t 'run-crons[24047]' -p warn
+ echo 'SCRIPT: suse.de-rkhunter exited with RETURNCODE = 1.'
SCRIPT: suse.de-rkhunter exited with RETURNCODE = 1.
+ STATUS=FAILURE
+ '[' -s /tmp/run-crons.a24049/run-crons.daily.24047 ']'
+ echo 'SCRIPT: output (stdout && stderr) follows'
SCRIPT: output (stdout && stderr) follows
+ echo ''

+ cat /tmp/run-crons.a24049/run-crons.daily.24047
Line: 
Warning: This operating system is not fully supported!
Line: Warning: This operating system is not fully supported!
Warning: Cannot find md5_not_known
Line: Warning: Cannot find md5_not_known
Watch out Root login possible. Possible risk!
Some errors has been found while checking. Please perform a manual check on this machine ipx20178
+ echo -e 'SCRIPT: suse.de-rkhunter\n------- END OF OUTPUT'
SCRIPT: suse.de-rkhunter
------- END OF OUTPUT
+ echo ''

+ echo ''

+ rm -f /tmp/run-crons.a24049/run-crons.daily.24047
---------------------------------------------------------------------------

Comment 1 Lars Vogdt 2007-11-28 16:21:32 UTC

looks like a duplicate of #341572

*** This bug has been marked as a duplicate of bug 341572 ***