From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] rkhunter --propupd not working since last updates installed
Date: Mon, 27 Jun 2011 10:12:36 -0400 [thread overview]
Message-ID: <4E088FD4.3090301@libertytrek.org> (raw)
Hello,
I have had rkhunter installed for a long time, been working well, system
was reporting clean...
On Saturday I did an emerge -uDN world and installed the available
updates (not a huge amount), then on Sunday morning, got a report about
6 files whose properties had changed, and I realized I forgot to run
--propupd command, so I did - but got the same email again, so it isn't
working (doesn't reset the files database so that it thinks they are
ok). I still get the same email/message about the same 6 files
properties being changed. I've tried running it 3 times now.
System checks summary
=====================
File properties checks...
Files checked: 144
Suspect files: 6
and from the log:
myhost : Mon Jun 27, 08:17:17 : ~
# grep Warn /var/log/rkhunter.log
[08:05:04] Info: Emailing warnings to 'root' using command '/bin/mail -s
"[rkhunter] Warnings found for ${HOST_NAME}"'
[08:05:30] /usr/bin/logger [ Warning ]
[08:05:30] Warning: The file properties have changed:
[08:05:38] /usr/bin/whereis [ Warning ]
[08:05:38] Warning: The file properties have changed:
[08:05:40] /sbin/fsck [ Warning ]
[08:05:40] Warning: The file properties have changed:
[08:05:47] /bin/dmesg [ Warning ]
[08:05:47] Warning: The file properties have changed:
[08:05:51] /bin/more [ Warning ]
[08:05:51] Warning: The file properties have changed:
[08:05:51] /bin/mount [ Warning ]
[08:05:51] Warning: The file properties have changed:
myhost : Mon Jun 27, 08:17:25 : ~
#
Anyone got any idea what could be causing this?
reply other threads:[~2011-06-27 14:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E088FD4.3090301@libertytrek.org \
--to=tanstaafl@libertytrek.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox