I've been leered at over things like 'this'. Hey, I'm good, but I'm not that good.Fred Barclay wrote:Yeah, sorry, I started a new thread a few hours ago about this. I was just letting you know that the link you sent did not show any open ports.
But as far as rkhunter itself goes, I do believe that the trouble was my not running the --propupd just as you mentioned. If you want to look at that thread, it's http://forums.linuxmint.com/viewtopic.p ... 2&t=207441 My last post there will have the log file you requested.
EDIT: Wait...what??? I was responding to a post by you that doesn't seem to be there.
Yes, some black stump stuff for sure.
I guess I edited a quoted reply incorrectly, or double-edited sounds about right.
No worries some folks say!!!
Here's the basic text:
All things will be more clear after the weekend and we are almost there...!!!You need to always rununder any the following conditionsCode: Select all
rkhunter --propupd
from the report, it appears you haven't run
- apt-get upgrade
- apt-get dist-upgrade
- apt-get dist-upgrade
- any edit of /etc/rkhunter.conf
and things have greatly changed since it was installed and/or first run.Code: Select all
rkhunter --propupd
Would you agree with my estimate?
We can squash most false-positives on Ubuntu-flavored hosts with 2 commands and one insert.
And we can't blindly do that until you (well 'we/me' with you) examine closely what is
generating those Warning:(s)
and that is in /var/log/rkhunter.log
can you pastebin that file before you do anything else with rkhunter?
and give back the short url?Code: Select all
cat /var/log/rkhunter.log | pastebin
Thank you.
Stuff I have left to 'do' after the weekend:
rkhunter
- Examine /var/log/rkhunter.log
- Verify Warnings there.
- Update /etc/rkhunter.conf
- Update propupd after
- Re-scan with rkhunter
- Goal is "No warnings were found while checking the system."
- Upgrade rkhunter to 1.4.3
- Rinse.
- Lather.
- Repeat.
- re-install with purge gufw
- Pray it works.