From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jim Nelson <james4765@verizon.net>
Cc: Wichert Akkerman <wichert@wiggy.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Question about /dev/mem and /dev/kmem
Date: Mon, 29 Nov 2004 11:45:18 +0000 [thread overview]
Message-ID: <1101728717.20220.8.camel@localhost.localdomain> (raw)
In-Reply-To: <41AAFE4E.7010308@verizon.net>
On Llu, 2004-11-29 at 10:47, Jim Nelson wrote:
> And what stops an attacker who's already gained root from doing a "cat "0" >
> /proc/sys/kernel/cap-bound" ?
If they already had root you've already lost.
An SELinux policy would probably be a lot more useful because you also
want to block ioperm/iopl
next prev parent reply other threads:[~2004-11-29 12:50 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
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 [this message]
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=1101728717.20220.8.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=james4765@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wichert@wiggy.net \
/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