All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>,
	chris friedhoff <chris@friedhoff.org>,
	Chris Wright <chrisw@sous-sol.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 1/1] security: introduce file posix caps
Date: Tue, 07 Nov 2006 21:27:15 +0900	[thread overview]
Message-ID: <45507BA3.9010700@kaigai.gr.jp> (raw)
In-Reply-To: <20061107034550.GA13693@sergelap.austin.ibm.com>

Hi, Serge.

I packaged the xattr extension of libcap, get/setfcaps command and
manual pages with original libcap-1.10-25.
See, http://www.kaigai.gr.jp/index.php?FrontPage#b556e50d

You can download RPM and SRPM package for the latest FC6 system.
There are no difference at its functionality, but the part of xattr
extension is moved into /lib/libcap.so.1.

Thanks,

Serge E. Hallyn wrote:
> Implement file posix capabilities.  This allows programs to be given
> a subset of root's powers regardless of who runs them, without
> having to use setuid and giving the binary all of root's powers.
> 
> This version works with Kaigai Kohei's userspace tools, found at
> http://www.kaigai.gr.jp/pub/fscaps-1.0-kg.src.rpm under
> http://www.kaigai.gr.jp/index.php?FrontPage#b556e50d.
> 
> (For more information on how to use, Chris Friedhoff has posted a nice
> page on his use of file caps at http://www.friedhoff.org/fscaps.html.
-- 
KaiGai Kohei <kaigai@kaigai.gr.jp>

  reply	other threads:[~2006-11-07 12:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07  3:45 [PATCH 1/1] security: introduce file posix caps Serge E. Hallyn
2006-11-07 12:27 ` KaiGai Kohei [this message]
2006-11-07 14:56 ` Stephen Smalley
2006-11-07 15:10   ` Serge E. Hallyn
2006-11-07 15:26     ` Stephen Smalley
2006-11-07 16:43       ` Serge E. Hallyn
2006-11-07 18:45       ` Serge E. Hallyn
2006-11-07 21:54 ` Seth Arnold
2006-11-07 22:06   ` Serge E. Hallyn
2006-11-08  5:32   ` Serge E. Hallyn
2006-11-08 18:50     ` Chris Friedhoff

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=45507BA3.9010700@kaigai.gr.jp \
    --to=kaigai@kaigai.gr.jp \
    --cc=akpm@osdl.org \
    --cc=chris@friedhoff.org \
    --cc=chrisw@sous-sol.org \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=sds@tycho.nsa.gov \
    --cc=serue@us.ibm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.