public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <m.kerrisk@gmx.net>
To: <linux-kernel@vger.kernel.org>
Subject: Status of capabilities?
Date: Wed, 26 Jun 2002 14:40:45 +0200	[thread overview]
Message-ID: <000101c21d12$b643aae0$0200a8c0@MichaelKerrisk> (raw)

When I asked the question below a while back, I got no response.  Is there
really noone who can say anything about the future of capabilities?

Cheers

Michael

------- Forwarded message follows -------
Date sent:       Fri, 10 May 2002 08:28:55 +0200 (MEST)
From:            Michael Kerrisk <m.kerrisk@gmx.net>
Subject:         Status of capabilities?
To:              linux-kernel@vger.kernel.org

Gidday,

What are the current status and future of capabilites?  There seems to be no
up-to-date information on this anywhere.

It seems capabilities have been partly implemented since 2.2.  That is to
say:

1. The kernel checks (effective) capabilities when performing various
operations.

2. System calls are provided to raise and lower capabilties

What's still missing in 2.4, as far as I can see after reading the sources,
is the ability to set capabilities on executable files so that a process
gains those privileges when executing the file.  I recall seeing some
information somewhere saying this wasn't possible / wasn't going to happen
for ext2.  Is it on the drawing board for any file system?

Thanks

Michael



             reply	other threads:[~2002-06-26 13:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 12:40 Michael Kerrisk [this message]
2002-06-27  6:05 ` Status of capabilities? Dax Kelson
2002-06-27 12:57   ` Jesse Pollard
2002-06-27 20:54     ` Chris Wright
2002-06-27 22:52       ` Dax Kelson
2002-07-06 20:56         ` Chris Wright
  -- strict thread matches above, loose matches on Subject: below --
2002-06-28 13:20 Jesse Pollard
2002-05-10  6:28 Michael Kerrisk

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='000101c21d12$b643aae0$0200a8c0@MichaelKerrisk' \
    --to=m.kerrisk@gmx.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox