From: "Serge E. Hallyn" <serue@us.ibm.com>
To: lkml <linux-kernel@vger.kernel.org>
Cc: linux-security-module@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Andrew Morgan <morgan@kernel.org>,
Chris Wright <chrisw@sous-sol.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Stephen Smalley <sds@epoch.ncsc.mil>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Natalie Protasevich <protasnb@gmail.com>
Subject: [PATCH] file capabilities: allow sigcont within session (v2)
Date: Wed, 31 Oct 2007 18:49:45 -0500 [thread overview]
Message-ID: <20071031234945.GA16455@sergelap.austin.ibm.com> (raw)
>From 5bff8967f45a35f858b96ca673d9bf98eac53d49 Mon Sep 17 00:00:00 2001
From: Serge E. Hallyn <serue@us.ibm.com>
Date: Wed, 31 Oct 2007 11:22:04 -0500
Subject: [PATCH 1/1] file capabilities: allow sigcont within session (v2)
(This is a proposed fix to http://bugzilla.kernel.org/show_bug.cgi?id=9247)
Allow sigcont to be sent to a process with greater capabilities
if it is in the same session. Otherwise, a shell from which
I've started a root shell and done 'suspend' can't be restarted
by the parent shell.
Also don't do file-capabilities signaling checks when uids for
the processes don't match, since the standard check_kill_permission
will have done those checks.
Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
---
security/commoncap.c | 9 +++++++++
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/security/commoncap.c b/security/commoncap.c
index bf67871..4de6857 100644
--- a/security/commoncap.c
+++ b/security/commoncap.c
@@ -526,6 +526,15 @@ int cap_task_kill(struct task_struct *p, struct siginfo *info,
if (info != SEND_SIG_NOINFO && (is_si_special(info) || SI_FROMKERNEL(info)))
return 0;
+ /* if tasks have same uid, then check_kill_permission did check */
+ if (current->uid == p->uid || current->euid == p->uid ||
+ current->uid == p->suid || current->euid == p->suid)
+ return 0;
+
+ /* sigcont is permitted within same session */
+ if (sig == SIGCONT && (task_session_nr(current)==task_session_nr(p)))
+ return 0;
+
if (secid)
/*
* Signal sent as a particular user.
--
1.5.1.1.GIT
next reply other threads:[~2007-10-31 23:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-31 23:49 Serge E. Hallyn [this message]
2007-11-01 1:27 ` [PATCH] file capabilities: allow sigcont within session (v2) Andrew Morgan
2007-11-01 4:47 ` Andrew Morgan
2007-11-01 12:07 ` Stephen Smalley
2007-11-01 13:47 ` Serge E. Hallyn
2007-11-01 20:12 ` Theodore Tso
2007-11-02 1:54 ` Theodore Tso
2007-11-03 21:31 ` Andrew Morgan
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=20071031234945.GA16455@sergelap.austin.ibm.com \
--to=serue@us.ibm.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=morgan@kernel.org \
--cc=protasnb@gmail.com \
--cc=rjw@sisk.pl \
--cc=sds@epoch.ncsc.mil \
--cc=tytso@mit.edu \
/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