One thing to be wary of is the number of false-positives coming from chkrootkit. It seems to alert for just about every .* directory it can find on the system, including bits of JDK, volatile tmpfs, and is subject to race-conditions falsely complaining about “hidden” processes when all that’s happened is a few have died since it compared lists. Processes in detached screen sessions seem to show up based on their ttys not being found in utmp. It seems to think my init is `INFECTED’ which is complete hokum. All this because it’s a kludged-up load of shell-scripts relying on grep for ill-defined regexp-matches.
So. I’m with rkhunter - it’s far more intelligent in operation, doing things like checking for changes in passwd and root-equivalent users between runs, for example. I can and do run both on all dozen-or-more debian boxes, but I take rkhunter far more seriously and only look for *changes* in output from chkrootkit.
Alberto Adrián Schiano on 05 Nov 09Linux Outlaws is a podcast about Linux and free and open source software. We are normal users like yourself rather than part of the in-crowd of community leaders and hardcore kernel hackers. On the show, we talk about interesting news and developments and stuff that we come across in our daily usage of Linux, often with a serious attitude and a humorous angle (the podcast has been described as being "very laid-back" by listeners and reviewers alike). We don't claim to be gurus or experts on anything, but we're trying very hard to provide you with a good time and interesting information.
