public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: carbonated beverage <ramune@net-ronin.org>
To: Olaf Dietsche <olaf.dietsche@t-online.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: capable open_port() check wrong for kmem
Date: Wed, 11 Dec 2002 14:38:57 -0800	[thread overview]
Message-ID: <20021211223857.GA23741@net-ronin.org> (raw)
In-Reply-To: <87fzt6nm6n.fsf@goat.bogus.local>

On Tue, Dec 10, 2002 at 12:33:04PM +0100, Olaf Dietsche wrote:
[snip]
> You may want to look at this thread:
> <http://groups.google.com/groups?threadm=87smza1p7f.fsf%40goat.bogus.local>

Hmm.

Okay, which approach is generally accpetible for inclusion into the kernel?
1) Nuke CAP_SYS_RAWIO check.  If the permissions on /dev/kmem is wrong,
tough.  It shouldn't be root:root 0666 in the first place anyways.
2) Add CAP_SYS_KMEM for read-only access, check for CAP_SYS_RAWIO for
the write case.
3) Special case /dev/kmem in open_port.

or:

4) Even if an application doesn't need write access to /dev/kmem, require
it to open /dev/kmem O_RDWR, as  it makes life easier for many people,
especially when modifying the kernel at run-time to hijack sysca... um, do
creative updates. :)

I'd prefer #1 or #2, but the discussion seems to have ended during the last
time the issue was brought up.

-- DN
Daniel

      reply	other threads:[~2002-12-11 22:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10  3:22 capable open_port() check wrong for kmem carbonated beverage
2002-12-10  5:45 ` David Wagner
2002-12-10  6:27   ` David Schwartz
     [not found]   ` <20021210064134.GA17928@net-ronin.org>
2002-12-10  6:51     ` carbonated beverage
2002-12-12  0:43       ` Chris Wright
2002-12-12  1:38         ` carbonated beverage
2002-12-12  2:11           ` Chris Wright
2002-12-10 11:33 ` Olaf Dietsche
2002-12-11 22:38   ` carbonated beverage [this message]

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=20021211223857.GA23741@net-ronin.org \
    --to=ramune@net-ronin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf.dietsche@t-online.de \
    /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