From: Linda Walsh <lkml@tlinx.org>
To: Andre Tomt <andre@tomt.net>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Save 320K on production machines?
Date: Mon, 27 Mar 2006 02:05:16 -0800 [thread overview]
Message-ID: <4427B8DC.6090406@tlinx.org> (raw)
In-Reply-To: <44266F61.9050209@tomt.net>
Andre Tomt wrote:
> Linda Walsh wrote:
> <snip>
>> To minimize
>> problems, I disable unused hardware, and all _used_ hardware
>> is compiled in (no module loading overhead, no chances for
>> arbitrary code insertion).
>
> FYI, rootkits have been able to cope with inserting kernel code
> without using the modules support for ages. It is only makes it
> marginally harder.
>
---
True, but that's the point. People break into systems with
passwords. Just because passwords aren't 100% effective in
protecting systems doesn't mean we don't use them. :-)
The point is to "minimize" a vulnerability profile.
I'm wondering why unused code is required to be compiled
in to standard kernels. It seems very un-linux like -- more like
Windows that has support for everything compiled in.
Reducing code bloat is not just a good idea for embedded systems.
It's good for performance and security if for no other reason that
there are fewer lines that could go wrong. :-)
-l
next prev parent reply other threads:[~2006-03-27 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 8:31 Save 320K on production machines? Linda Walsh
2006-03-26 9:24 ` Jan Engelhardt
2006-03-26 10:06 ` Adrian Bunk
2006-03-27 10:22 ` Linda Walsh
2006-03-27 11:36 ` Paulo Marques
2006-03-30 21:34 ` Linda Walsh
2006-03-31 9:43 ` Adrian Bunk
2006-03-31 9:48 ` Jörn Engel
2006-03-26 10:39 ` Andre Tomt
2006-03-27 10:05 ` Linda Walsh [this message]
2006-03-28 14:29 ` Jan Engelhardt
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=4427B8DC.6090406@tlinx.org \
--to=lkml@tlinx.org \
--cc=andre@tomt.net \
--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 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.