From: "Richard B. Johnson" <root@chaos.analogic.com>
To: joe briggs <jbriggs@briggsmedia.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Help with virus/hackers
Date: Thu, 17 Apr 2003 09:55:30 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0304170932490.15993@chaos> (raw)
In-Reply-To: <200304171015.13474.jbriggs@briggsmedia.com>
On Thu, 17 Apr 2003, joe briggs wrote:
> Please redirect me if this is not the appropriate place for this post.
>
> I have several Debian/Woody/2.4.19 webserver/firewalls at various locations
> that seem to have been hacked or victum of a worm or virus. It is hard to
> articulate exactly the symptoms since it quickly brings the system down, but
> here is what I know so far:
>
[SNIPPED...]
It is unlikely that one of those Windows worms or virii affected
your system. It is more likely that you simply have a trashed
file-system. To check for an invasion, do the following.
(1) Disconnect the network wire.
(2) Boot with init=/bin/bash
(3) `fsck` each file-system slice by hand. Look in /etc/fstab
to get them all.
(4) Execute `mount -a` to mount all the slices in the correct
order.
(5) Examine /etc/inetd.conf (if one exists). If you see an
unusual entry near the end, you have been 'rooted'. Newer
systems use xinetd and won't get invaded this way.
(6) Check /etc/passwd for a strange account.
(7) Check /bin/login for a new file-date.
(8) Check /usr/sbin/sendmail for a new file-date.
Check /usr/sbin/inetd ""
Check /usr/sbin/xinetd ""
Check /usr/sbin/syslogd ""
Check /usr/sbin/klogd ""
Check /usr/sbin/in.* ""
If any of these files have recent writes, tar off all user-data
and completely install Linux again (from a distribution) from scratch.
Do not use a recent backup. It could have already been invaded.
If none of these have recent writes, just change the password on
the root account and be happy. You just has some file-system
corruption and you can fix up /etc/DIR_COLORS (for your color-ls
problem) and fix /etc/profile or /root/.bashrc, /root/.profile
to fix the bad environment variables created by these scripts.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.
next prev parent reply other threads:[~2003-04-17 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 14:15 joe briggs
2003-04-17 12:42 ` Alan Cox
2003-04-17 13:55 ` Richard B. Johnson [this message]
2003-04-17 14:12 ` Alan Cox
2003-04-17 15:31 ` John Jasen
2003-04-17 15:45 ` John Bradford
2003-04-17 16:26 ` Alan Cox
2003-04-17 18:00 ` John Bradford
2003-04-17 17:17 ` Christopher Curtis
2003-04-17 14:12 ` Alan Cox
2003-04-17 16:34 Kenny Mann
2003-04-17 17:24 ` Leonard Milcin, Jr
2003-04-17 18:12 Kenny Mann
2003-04-17 20:56 Kenny Mann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.53.0304170932490.15993@chaos \
--to=root@chaos.analogic.com \
--cc=jbriggs@briggsmedia.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®