Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: understanding chkrootkit and rkhunter logs |
|---|---|
| Date: | Wed, 9 May 2007 08:57:37 +0200 |
On Tuesday 08 May 2007 11:56, acattelan@gmail.com wrote:
Hi, I'm sorry for asking a totally newbie question but I haven't found an answer to this. I'm really curious and concerned about what is reported by the chkrootkit and rkhunter on my Debian Etch home server. Here's what I get when I run them: CHKROOTKIT: Searching for suspicious files and dirs, it may take a while... /usr/lib/xulrunner/.autoreg /lib/init/rw/.ramfs Checking `sniffer'... lo: not promisc and no packet sniffer sockets eth0: PACKET SNIFFER(/sbin/dhclient[2181]) In the system mail I also get this: /etc/cron.daily/chkrootkit: The following suspicious files and directories were found: /usr/lib/xulrunner/.autoreg /lib/init/rw/.ramfs eth0: PACKET SNIFFER(/sbin/dhclient[2136]) RKHUNTER reports this: * Filesystem checks Checking /dev for suspicious files... [ OK ] Scanning for hidden files... [ Warning! ] --------------- /etc/.pwd.lock /dev/.static /dev/.udev /dev/.initramfs /dev/.initramfs-tools --------------- Please inspect: /dev/.static (directory) /dev/.udev (directory) /dev/.initramfs (directory) Is this something to be worried about? How can I investigate further into these two issues?
/dev/.initramfs/ is afaik created by the initramfs-tools during boot. if you want to investigate more search for your initramfs scripts and take a closer look at it. The same is for /dev/.udev Maybe you should take a closer look on the other files and see whats inside of them - but I guess they will be fine too: /etc/.pwd.lock /dev/.static /usr/lib/xulrunner/.autoreg /lib/init/rw/.ramfs Best regards, Juergen
Thanks, Ale.
-- Jürgen Repolusk +43 650 5661250 http://jvr.at/serendipity/
pgpgT3t5DFqur.pgp
Description: PGP signature
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: understanding chkrootkit and rkhunter logs, Oren Held |
|---|---|
| Next by Date: | Re: understanding chkrootkit and rkhunter logs, Clinton E. Troutman |
| Previous by Thread: | Re: understanding chkrootkit and rkhunter logs, Oren Held |
| Next by Thread: | Re: understanding chkrootkit and rkhunter logs, Clinton E. Troutman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |