mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serue@us.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
	linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	morgan@kernel.org, buraphalinuxserver@gmail.com,
	lcapitulino@mandriva.com.br, stable@kernel.org
Subject: Re: [PATCH 1/1] file capabilities: remove cap_task_kill() (-git)
Date: Wed, 19 Mar 2008 16:20:07 -0500	[thread overview]
Message-ID: <20080319212007.GA12217@sergelap.austin.ibm.com> (raw)
In-Reply-To: <20080319141112.02981daf.akpm@linux-foundation.org>

Quoting Andrew Morton (akpm@linux-foundation.org):
> On Wed, 19 Mar 2008 11:56:35 -0500
> "Serge E. Hallyn" <serue@us.ibm.com> wrote:
> 
> > (resending once against -git.  I had sent against -stable in
> > http://lkml.org/lkml/2008/2/28/225.  Without this patch,
> > atd is broken at least on some distros.)
> 
> So this fix is needed in 2.6.24.x?

Yes it is.

> > The original justification for cap_task_kill() was as follows:
> > 
> > 	check_kill_permission() does appropriate uid equivalence checks.
> > 	However with file capabilities it becomes possible for an
> > 	unprivileged user to execute a file with file capabilities
> > 	resulting in a more privileged task with the same uid.
> > 
> > However now that cap_task_kill() always returns 0 (permission
> > granted) when p->uid==current->uid, the whole hook is worthless,
> > and only likely to create more subtle problems in the corner cases
> > where it might still be called but return -EPERM.  Those cases
> > are basically when uids are different but euid/suid is equivalent
> > as per the check in check_kill_permission().
> > 
> > One example of a still-broken application is 'at' for non-root users.
> 
> This 2.6.25-rc6 patch doesn't apply correctly to 2.6.24.  I can't find a
> *formal* copy of your 2.6.24 patch on stable@kernel.org, so perhaps a
> resend for -stable is in order.

Argh, yes, will do.  Thanks.

-serge

  reply	other threads:[~2008-03-19 22:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-19 16:56 Serge E. Hallyn
2008-03-19 18:12 ` Luiz Fernando N. Capitulino
2008-03-19 21:11 ` Andrew Morton
2008-03-19 21:20   ` Serge E. Hallyn [this message]
2008-03-19 23:46 ` Andrew Morton
2008-03-20  2:13   ` Linus Torvalds
2008-03-20  3:18     ` Serge E. Hallyn
2008-03-20  4:17       ` Linus Torvalds
2008-03-20 13:25         ` Serge E. Hallyn
2008-03-20 15:29       ` Casey Schaufler

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=20080319212007.GA12217@sergelap.austin.ibm.com \
    --to=serue@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=buraphalinuxserver@gmail.com \
    --cc=lcapitulino@mandriva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=morgan@kernel.org \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®