From: Matan Peled <chaosite@gmail.com>
To: Jim Nelson <james4765@verizon.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about /dev/mem and /dev/kmem
Date: Mon, 29 Nov 2004 06:45:02 +0200 [thread overview]
Message-ID: <41AAA94E.8090001@gmail.com> (raw)
In-Reply-To: <41AA9E26.4070105@verizon.net>
Jim Nelson wrote:
> I was looking at some articles about rootkits on monolithic kernels,
and had a thought. Would a kernel config option to disable write >
access to /dev/mem and /dev/kmem be a workable idea?
Yes, its a workable idea, and in fact, has already been implemented in
grsecurity.
http://www.grsecurity.net/features.php
next prev parent reply other threads:[~2004-11-29 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 3:57 Question about /dev/mem and /dev/kmem Jim Nelson
2004-11-29 4:45 ` Matan Peled [this message]
2004-11-29 8:04 ` Arjan van de Ven
2004-11-29 9:39 ` Wichert Akkerman
2004-11-29 10:47 ` Jim Nelson
2004-11-29 11:45 ` Alan Cox
2004-11-29 12:36 ` Wichert Akkerman
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=41AAA94E.8090001@gmail.com \
--to=chaosite@gmail.com \
--cc=james4765@verizon.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.