All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Allison <fireflyblue@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Kernel Rootkits
Date: Fri, 15 Apr 2005 21:19:57 +0200	[thread overview]
Message-ID: <426013DD.6050905@tomt.net> (raw)
In-Reply-To: <20050415183738.GR17865@csclub.uwaterloo.ca>

Lennart Sorensen wrote:
> Well you could build a monilithic kernel with module loading turned off
> entirely, but that doesn't prevent replacing libc which most programs
> use to make those system calls.

As pointed out elsewhere, modules is not the only way to load kernel 
code live. Modules is just a cleaner interface for it. Rootkits capable 
of loading their kernel code without involving the module system has 
existed for ages.

> Could make the filesystem readonly,
> that would prevent writing a module to load into the kernel, and
> replacing libc as long as you make it imposible to remount the
> filesystem at all.

Don't hold your breath - code can be inserted without involving actual 
files. It just makes things less persistent.

-- 
Cheers,
André Tomt

  reply	other threads:[~2005-04-15 19:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 18:15 Kernel Rootkits Allison
2005-04-15 18:33 ` Petr Baudis
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 [this message]
2005-04-15 18:40 ` Daniel Souza
2005-04-15 19:21   ` Lee Revell
2005-04-15 19:40     ` Daniel Souza
  -- 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 17:33 Malita, Florin
2005-04-15 18:08 ` Lee Revell
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=426013DD.6050905@tomt.net \
    --to=andre@tomt.net \
    --cc=fireflyblue@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.