From: Lee Revell <rlrevell@joe-job.com>
To: "Malita, Florin" <Florin.Malita@Glenayre.com>
Cc: linux-os@analogic.com, Allison <fireflyblue@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Kernel Rootkits
Date: Fri, 15 Apr 2005 14:08:14 -0400 [thread overview]
Message-ID: <1113588494.23659.9.camel@mindpipe> (raw)
In-Reply-To: <1113586421.26941.121.camel@scox.glenatl.glenayre.com>
On Fri, 2005-04-15 at 13:33 -0400, Malita, Florin wrote:
> On Fri, 2005-04-15 at 13:16 -0400, Richard B. Johnson wrote:
> > I'm not sure there really are any "kernel" rootkits. You need to be
> > root to install a module and you need to be root to replace a kernel
> > with a new (possibly altered) one. If you are root, you don't
> > need an exploit.
>
> rootkit != exploit
>
> The exploit is used to gain root privileges while the rootkit is used
> after that to install & hide backdoors, sniffers, keyloggers etc.
>
> http://en.wikipedia.org/wiki/Rootkit
>
"Rootkit" is sometimes used to refer to the all-in-one bundle, that
contains the exploit and the tools the attacker installs once they are
in.
OT: the dumbest rootkit I ever came across came from someone who cracked
one of our nameservers via an openssh hole. They were careful to
replace netstat, ps, etc but apparently didn't know about lsof, which
was the first thing I tried of course. Then they hid the old binaries
in a subdirectory of /dev (because no one would ever look there).
Thanks to the "l33t skillz" of the author, I didn't even have to wipe
the machine to recover it.
Lee
next prev parent reply other threads:[~2005-04-15 18:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 17:33 Kernel Rootkits Malita, Florin
2005-04-15 18:08 ` Lee Revell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-15 19:15 Allison
2005-04-15 19:38 ` Daniel Souza
2005-04-15 18:15 Allison
2005-04-15 18:34 ` Daniel Souza
2005-04-15 18:36 ` Lee Revell
2005-04-15 18:37 ` Lennart Sorensen
2005-04-15 19:19 ` Andre Tomt
2005-04-15 18:40 ` Daniel Souza
2005-04-15 19:21 ` Lee Revell
2005-04-15 19:40 ` Daniel Souza
2005-04-15 16:02 Allison
2005-04-15 17:16 ` Richard B. Johnson
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=1113588494.23659.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Florin.Malita@Glenayre.com \
--cc=fireflyblue@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
/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