From: "Michael H. Warfield" <mhw@wittsend.com>
To: Alex Buell <alex.buell@tahallah.demon.co.uk>
Cc: Alexander Viro <viro@math.psu.edu>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>, Adam <adam@eax.com>,
Mailing List - Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Duplicate '..' in /lib
Date: Mon, 16 Jul 2001 22:22:15 -0400 [thread overview]
Message-ID: <20010716222215.A4695@alcove.wittsend.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0107160128320.26491-100000@weyl.math.psu.edu> <Pine.LNX.4.33.0107160727520.634-100000@tahallah.demon.co.uk>
In-Reply-To: <Pine.LNX.4.33.0107160727520.634-100000@tahallah.demon.co.uk>; from alex.buell@tahallah.demon.co.uk on Mon, Jul 16, 2001 at 07:30:01AM +0100
On Mon, Jul 16, 2001 at 07:30:01AM +0100, Alex Buell wrote:
> On Mon, 16 Jul 2001, Alexander Viro wrote:
> > Alex, could you do strace of that? It would clarify the situation.
> Unfortunately there's no working version of strace for the sparc32-linux
> platform. :o( If anyone knows better, I'd be infinitely grateful - mail me
> privately.
> As it turns out, the extraneous '..' is actually a file. I did a rm ..*,
> which left the original .. directory alone but removed the .. file. Did a
> e2fsck on reboot, no problems found.
That's like the old game of adventure when you wave the wand and
it replies "Nothing obvious happens" just before you step into quicksand
(if you waved it an even number of times).
You got problems. There should be a reason for that file and it
ain't good. It ain't good AT ALL. It's a stock "cracker" trick for
hiding something (lame, I know). You need to go over that system with
a fine toothed comb. Boot from secure media, like the LinuxCare BBC
(Bootable Business Card), and sweep that sucker. You can use rpm to
verify the packages to begin with... Don't trust ANY executable on
the system itself.
You HAVE to boot from other media. Some of these suckers have
Linux kernel modules (we'll keep it a little on topic here) like Adore
and KIS that hide processes, connections, services, and files. You can
not trust your kernel if you may have been compromised.
> --
> Hey, they *are* out to get you, but it's nothing personal.
No joke... And I do believe they done got you.
> http://www.tahallah.demon.co.uk
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
(The Mad Wizard) | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
next prev parent reply other threads:[~2001-07-17 2:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-16 4:50 Alex Buell
2001-07-16 5:07 ` Ben Collins
2001-07-16 5:08 ` Ignacio Vazquez-Abrams
2001-07-16 5:11 ` Adam
2001-07-16 5:16 ` Albert D. Cahalan
2001-07-16 5:38 ` Alexander Viro
2001-07-16 5:55 ` David Luyer
2001-07-16 6:30 ` Alex Buell
2001-07-16 8:07 ` Wichert Akkerman
2001-07-16 8:16 ` J Troy Piper
2001-07-17 2:22 ` Michael H. Warfield [this message]
2001-07-17 10:26 ` Alex Buell
2001-07-17 12:33 ` Michael H. Warfield
2001-07-17 12:44 ` Alex Buell
2001-07-17 12:58 ` Michael H. Warfield
2001-07-17 13:00 ` Large memory oops/odd behaviour Linux 2.2, seeking recommendations Mr. James W. Laferriere
2001-07-16 5:32 ` Duplicate '..' in /lib Alex Buell
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=20010716222215.A4695@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=acahalan@cs.uml.edu \
--cc=adam@eax.com \
--cc=alex.buell@tahallah.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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®