From: Andrew Morton <akpm@linux-foundation.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
morgan@kernel.org, buraphalinuxserver@gmail.com,
lcapitulino@mandriva.com.br
Subject: Re: [PATCH 1/1] file capabilities: remove cap_task_kill() (-git)
Date: Wed, 19 Mar 2008 16:46:01 -0700 [thread overview]
Message-ID: <20080319164601.d105e3df.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080319165635.GH5935@sergelap.ibm.com>
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.)
>
> 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 patch removes cap_task_kill().
umm,
security/smack/smack_lsm.c: In function 'smack_task_kill':
security/smack/smack_lsm.c:1122: error: implicit declaration of function 'cap_task_kill'
next prev parent reply other threads:[~2008-03-20 0:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 16:56 [PATCH 1/1] file capabilities: remove cap_task_kill() (-git) 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
2008-03-19 23:46 ` Andrew Morton [this message]
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=20080319164601.d105e3df.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=buraphalinuxserver@gmail.com \
--cc=lcapitulino@mandriva.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=serue@us.ibm.com \
--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 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.