warning, got bogus tcp line.

I was presented with this error when using ChkRootKit-0.39a. I have alos found a post or two online referring to the same error with respect to netstat.

Of course there was no answer to this person's question...

I was hoping you all could help me...

"Warning, got bogus TCP line."

Is that coming from ChkRootKit or your kernel?

not certain...

Print your output, maybe seeing the error in context will help.

well... it was contained in the body of an email that I send my self via this cron job:

sh /usr/sbin/chkrootkit-0.39a/chkrootkit |grep -v "not" |mail -s "CHKROOTKIT on $(hostname)"

This is the email:

From: Cron Daemon <root@www.mydomain.com>
To: root@www.mydomain.com
Subject: Cron <root@www> sh /usr/sbin/chkrootkit-0.39a/chkrootkit |grep -v "not" |mail -s "CHKROOTKIT on $(hostname)" wendels@mydomain.com
Date: 19 Mar 2003 08:51:09 -0500

warning, got bogus tcp line.

This is the standard out recieved when running chkrootkit. I duplicated the output yesterday running chkrootkit from the command line. Didn't get the same error today...

Not certain what to make of this...

and thx for you're help...

kick-ass quote btw too...

I may steal this in the future...

Man that is a mystery if you're not getting the same output today...

My only experience with chkrootkit is running myself (ie: when I feel like it) from the command-line, so I tend to look at everything...

The problem with what you've posted is that it doesn't really say where this is from....

like when chkrootkit prints out a line:

checking for (whatever).....no

curious...

ya... if I have time (which is most unlikely) I will fish through the source and see what exactly is causing this...

/me shrugs

Thanks again though!

Can you run chkrootkit in a terminal and see if you get this 'bogus tcp line' error. I'm not sure if this an e-mail error or a message from chkrootkit.

chkrootkit will check things like sniffer logs, your syslogs and other log files for potential hack attempts / exploits and so forth.

I highly suspect that it detected something in your syslog (possibly a netfilter log entry) which lent it to believe someone was trying to compromise your box.

Easiest way to find out is to simply run chkrootkit (without the grep -v) and see *WHERE* it displays the problem.

You'll see something like this :

Checking `aliens'... no suspect files
Searching for sniffer's logs, it may take a while... nothing found
Searching for HiDrootkit's default dir... nothing found
Searching for t0rn's default files and dirs... nothing found
Searching for t0rn's v8 defaults... nothing found
Searching for Lion Worm default files and dirs... nothing found
Searching for RSHA's default files and dir... nothing found
Searching for RH-Sharpe's default files... nothing found
Searching for Ambient's rootkit (ark) default files and dirs... nothing found
Searching for suspicious files and dirs, it may take a while...

and will be able to determine where'bouts it detected 'something bogus'

Slick.

thanks guys...

I had run chkrootkit via the command line as soon as I received this email yesterday...

if I remember correctly, the error was received after all of the usual output was displayed...

this box has since been rebooted and has not seen the error again...