mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: devzero@web.de
Cc: Nix <nix@esperi.org.uk>, davej@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: another kconfig target for building monolithic kernel (for security) ?
Date: Sun, 30 Apr 2006 15:15:14 +0200	[thread overview]
Message-ID: <1146402915.20760.6.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1094806367@web.de>

On Sun, 2006-04-30 at 14:31 +0200, devzero@web.de wrote:
> hello !
> 
> "Unfortunately, disabling /dev/mem will break many things, including X and potentially many other user-space programs"
> (-> http://lwn.net/2001/0419/security.php3 )

not if you do it carefully like we did for Fedora...

> 
> "The /dev/mem and /dev/kmem character special files provide access to a pseudo device driver that allows read and write access to system memory or I/O address space. Typically, these special files are used by operating system utilities and commands (such as sar, iostat, and vmstat) to obtain status and statistical information about the system" (ok, this is for AIX, does this apply for linux, too? -> http://publib.boulder.ibm.com/infocenter/pseries/v5r3/index.jsp?topic=/com.ibm.aix.doc/files/aixfiles/mem.htm )


/dev/kmem isn't used by much of anything except debugging, so having
that a config option is reasonable. for /dev/mem it's enough to disable
all access to 'what the kernel sees as RAM' with the lower 1Mb as
exception..


  reply	other threads:[~2006-04-30 13:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-30 12:31 devzero
2006-04-30 13:15 ` Arjan van de Ven [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-30 23:07 devzero
2006-04-29 17:11 devzero
2006-04-29 13:03 devzero
2006-04-29 16:43 ` Dave Jones
2006-04-29 21:22   ` Arjan van de Ven
2006-04-30 10:57     ` Nix

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=1146402915.20760.6.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=davej@redhat.com \
    --cc=devzero@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nix@esperi.org.uk \
    /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

all inboxes | Powered by JetHome®