public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dax Kelson <dax@gurulabs.com>
To: Michael Kerrisk <m.kerrisk@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Status of capabilities?
Date: 27 Jun 2002 00:05:25 -0600	[thread overview]
Message-ID: <1025157926.1652.35.camel@mentor> (raw)
In-Reply-To: <000101c21d12$b643aae0$0200a8c0@MichaelKerrisk>

On Wed, 2002-06-26 at 06:40, Michael Kerrisk wrote:

> 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?

The 2.5 VFS supports Extended Attributes (since 2.5.3). I think the plan
was use EAs to store capabilities. So I believe that the infrastructure
is in place, someone with the proper skills just needs to:

1. Define how capabilities will be stored as a EA
2. Teach fs/exec.c to use the capabilities stored with the file
3. Write lscap(1)
4. Write chcap(1)
5. Audit/fix all SUID root binaries to use capabilities
6. Set appropriate capabilities with for each with chcap(1) and then:
   # find / -type f -perm -4000 -user root -exec chmod u-s {} \;
7. Party and snicker in the general direction of that OS with the slogan
"One remote hole in the default install, in nearly 6 years!"

Dax Kelson
Guru Labs

Disclaimer: I could be completely wrong on any or all of the above


  reply	other threads:[~2002-06-27  6:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-26 12:40 Status of capabilities? Michael Kerrisk
2002-06-27  6:05 ` Dax Kelson [this message]
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=1025157926.1652.35.camel@mentor \
    --to=dax@gurulabs.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.kerrisk@gmx.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