From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bert hubert <ahu@ds9a.nl>
Cc: David Lang <david.lang@digitalinsight.com>,
Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devik@cdi.cz, aebr@win.tue.nl
Subject: Re: [PATCH] Allow /dev/{,k}mem to be disabled to prevent kernel from being modified easily
Date: 04 Aug 2003 14:10:42 +0100 [thread overview]
Message-ID: <1060002642.416.9.camel@dhcp22.swansea.linux.org.uk> (raw)
In-Reply-To: <20030803214738.GA16129@outpost.ds9a.nl>
On Sul, 2003-08-03 at 22:47, bert hubert wrote:
> As to what Alan said about LSM, I've yet to see how to do that in a
> reasonable way. But I didn't look too hard.
Just refuse anything needing CAP_SYS_RAWIO at all times. Thats why this
capability flag exists. Or with SELinux you can create a role which has
RAWIO access but is very limited in other ways (eg "Only my X server",
or "only the firmware loader for my serial card") and which is tainted
if anything else touches those files
Alan
next prev parent reply other threads:[~2003-08-04 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 18:09 bert hubert
2003-08-03 19:11 ` Willy Tarreau
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 [this message]
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=1060002642.416.9.camel@dhcp22.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=aebr@win.tue.nl \
--cc=ahu@ds9a.nl \
--cc=akpm@osdl.org \
--cc=david.lang@digitalinsight.com \
--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 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®