From: Willy Tarreau <willy@w.ods.org>
To: bert hubert <ahu@ds9a.nl>,
linux-kernel@vger.kernel.org, akpm@osdl.org, devik@cdi.cz
Subject: Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily
Date: Sun, 3 Aug 2003 21:11:02 +0200 [thread overview]
Message-ID: <20030803191102.GA29616@alpha.home.local> (raw)
In-Reply-To: <20030803180950.GA11575@outpost.ds9a.nl>
On Sun, Aug 03, 2003 at 08:09:50PM +0200, bert hubert wrote:
> It blocks attempts by rootkits, such as devik's SucKIT, to hide themselves.
>
> It is not a final solution but it raises the bar a lot. Please apply.
>
> By default, nothing is changed, but I'd turn this feature on on servers
> without X. Patch:
Why not make this change dynamic instead ? eg : your system boots unlocked,
and definitely locks /dev/{,k}mem once you do something such as
echo foo > /proc/path_to_magic_entry
So the same config can be used with kernel with and without X, it's just a
matter of runtime configuration. It could even be a sysctl, as long as there's
no way to unset it.
Regards,
Willy
next prev parent reply other threads:[~2003-08-03 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 18:09 [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily bert hubert
2003-08-03 19:11 ` Willy Tarreau [this message]
2003-08-03 19:18 ` bert hubert
2003-08-03 20:26 ` Willy Tarreau
2003-08-03 21:37 ` Andries Brouwer
2003-08-03 19:32 ` Andrew Morton
2003-08-03 20:45 ` bert hubert
2003-08-03 20:52 ` Wichert Akkerman
2003-08-03 21:00 ` Andrew Morton
2003-08-03 21:33 ` David Lang
2003-08-03 21:47 ` bert hubert
2003-08-04 13:10 ` Alan Cox
2003-08-03 20:14 ` Matan Ziv-Av
2003-08-03 21:02 ` Alan Cox
2003-08-03 21:08 ` Erik Andersen
2003-08-04 12:30 ` eliezer
2003-08-04 9:37 ` devik
2003-08-04 13:46 ` bert hubert
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=20030803191102.GA29616@alpha.home.local \
--to=willy@w.ods.org \
--cc=ahu@ds9a.nl \
--cc=akpm@osdl.org \
--cc=devik@cdi.cz \
--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.