mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	Stephen Smalley <sds@tycho.nsa.gov>,
	James Morris <jmorris@namei.org>,
	Chris Wright <chrisw@sous-sol.org>,
	KaiGai Kohei <kaigai@kaigai.gr.jp>,
	Chris Friedhoff <chris@friedhoff.org>,
	Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: security: introduce file caps
Date: Thu, 23 Nov 2006 00:22:07 -0800	[thread overview]
Message-ID: <20061123002207.5e18bade.akpm@osdl.org> (raw)
In-Reply-To: <20061123001458.fe73f64a.akpm@osdl.org>

On Thu, 23 Nov 2006 00:14:58 -0800
Andrew Morton <akpm@osdl.org> wrote:

> On Mon, 13 Nov 2006 21:06:55 -0600
> "Serge E. Hallyn" <serue@us.ibm.com> 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.
> 
> With this patch applied, my X server fails to exit when I do the normal
> logout thing from the KDE menus.

After a manual kill of the X server I see on the VT:

xinit: Operation not permitted (errno 1): Can't kill X server


  reply	other threads:[~2006-11-23  8:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14  3:06 Serge E. Hallyn
2006-11-15  8:55 ` Chris Friedhoff
2006-11-23  8:14 ` Andrew Morton
2006-11-23  8:22   ` Andrew Morton [this message]
     [not found]     ` <20061123131203.f7b6972f.chris@friedhoff.org>
2006-11-23 18:39       ` Andrew Morton
2006-11-23 21:41         ` Serge E. Hallyn
2006-11-23 23:21           ` Chris Friedhoff
2006-11-24 16:16         ` file caps: permit unsafe signaling when CONFIG_FS_CAPS=n Serge E. Hallyn
2006-11-24 18:17           ` Serge E. Hallyn
2006-11-25 21:19             ` 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=20061123002207.5e18bade.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adobriyan@gmail.com \
    --cc=chris@friedhoff.org \
    --cc=chrisw@sous-sol.org \
    --cc=jmorris@namei.org \
    --cc=kaigai@kaigai.gr.jp \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome