From: Keith Whyte <keith@media-solutions.ie>
To: linux-kernel@vger.kernel.org, linux-gcc@vger.kernel.org,
linux-admin@vger.kernel.org
Subject: solution: 2.4.18 fork & defunct child.
Date: Wed, 19 Nov 2003 20:42:38 -0600 [thread overview]
Message-ID: <3FBC2A1E.3010901@media-solutions.ie> (raw)
In-Reply-To: <3FB8E40F.EF61CA7@gmx.de>
Folks thanks to everyone who helped me out with this, I just found the
file 982235016-gtkrc-429249277 in /tmp
It kept reappearing as it tried to rm * -r in /tmp and
a quick google search led me to find out where it came from.
A few weeks ago i installed a binary that i got from a friends machine,
and i just checked his machine. It has the trojan also. that explains a
lot. It was a realserver binary (no longer available for d/l)and i ran
it once as root as it likes to listen on port 554, before I changed that
config and set up a user to run it. aggh. so easy to let something slip
through. never trust binaries... no matter where they come from.
Keith.
prev parent reply other threads:[~2003-11-20 2:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1069053524.3fb87654286b5@ssl.buz.org>
[not found] ` <3FB8E40F.EF61CA7@gmx.de>
2003-11-18 0:26 ` 2.4.18 fork & defunct child Keith Whyte
2003-11-18 1:00 ` Maciej Zenczykowski
2003-11-20 2:42 ` Keith Whyte [this message]
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=3FBC2A1E.3010901@media-solutions.ie \
--to=keith@media-solutions.ie \
--cc=linux-admin@vger.kernel.org \
--cc=linux-gcc@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).