| 1 |
Thanasis posted on Sat, 09 Oct 2010 12:28:26 +0300 as excerpted: |
| 2 |
|
| 3 |
> on 09/28/2010 12:34 PM Paul Stear wrote the following: |
| 4 |
>> Hi all, |
| 5 |
>> rkhunter runs every day and reports the following:- |
| 6 |
>> |
| 7 |
>> System checks summary |
| 8 |
>> ===================== |
| 9 |
>> |
| 10 |
>> File properties checks... |
| 11 |
>> Files checked: 142 |
| 12 |
>> Suspect files: 141 |
| 13 |
>> |
| 14 |
>> Rootkit checks... |
| 15 |
>> Rootkits checked : 246 |
| 16 |
>> Possible rootkits: 2 |
| 17 |
>> Rootkit names : Xzibit Rootkit, Dica-Kit Rootkit |
| 18 |
>> |
| 19 |
>> Any idea how I find and remove these Rootkits? |
| 20 |
>> |
| 21 |
>> thanks for any help |
| 22 |
>> Paul |
| 23 |
> Did you check the log file (/var/log/rkhunter.log)? |
| 24 |
|
| 25 |
If rkhunter is based on recorded file checksums, it's obviously going to |
| 26 |
have false-positives every time you update the files it checks, which |
| 27 |
tends to be reasonably frequently for many gentoo users (especially ~arch |
| 28 |
users), since given gentoo's rolling update nature. |
| 29 |
|
| 30 |
That's very possibly why it's saying 141 out of 142 files are suspect. A |
| 31 |
possible workaround would be running it before every update, to be sure, |
| 32 |
then running it after the update to update its checksums. |
| 33 |
|
| 34 |
But that doesn't explain the possible rootkits detected. Of course, |
| 35 |
depending on how it detects specific rootkits, that too may have false |
| 36 |
positives. If it happens to the big AV folks like Norton and McAfee, and |
| 37 |
it does, it's going to happen to everyone, occasionally. |
| 38 |
|
| 39 |
-- |
| 40 |
Duncan - List replies preferred. No HTML msgs. |
| 41 |
"Every nonfree program has a lord, a master -- |
| 42 |
and if you use the program, he is your master." Richard Stallman |
Archives