The patch titled
     capabilities: reset current->pdeath_signal when increasing capabilities
has been removed from the -mm tree.  Its filename was
     capabilities-reset-current-pdeath_signal-when-increasing-capabilities.patch

This patch was dropped because it was folded into 
implement-file-posix-capabilities.patch

------------------------------------------------------
Subject: capabilities: reset current->pdeath_signal when increasing capabilities
From: "Serge E. Hallyn" <[EMAIL PROTECTED]>

If running a program which has file capabilities which are not a subset of
the capabilities of the current task, reset pdeath_signal = 0 to prevent
the task parent from (deliberately) signaling a more privileged app.

Signed-off-by: Serge E. Hallyn <[EMAIL PROTECTED]>
Cc: Andrew Morgan <[EMAIL PROTECTED]>
Cc: Casey Schaufler <[EMAIL PROTECTED]>
Cc: Chris Wright <[EMAIL PROTECTED]>
Cc: James Morris <[EMAIL PROTECTED]>
Cc: Stephen Smalley <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 security/commoncap.c |    1 +
 1 files changed, 1 insertion(+)

diff -puN 
security/commoncap.c~capabilities-reset-current-pdeath_signal-when-increasing-capabilities
 security/commoncap.c
--- 
a/security/commoncap.c~capabilities-reset-current-pdeath_signal-when-increasing-capabilities
+++ a/security/commoncap.c
@@ -267,6 +267,7 @@ void cap_bprm_apply_creds (struct linux_
        if (bprm->e_uid != current->uid || bprm->e_gid != current->gid ||
            !cap_issubset (new_permitted, current->cap_permitted)) {
                set_dumpable(current->mm, suid_dumpable);
+               current->pdeath_signal = 0;
 
                if (unsafe & ~LSM_UNSAFE_PTRACE_CAP) {
                        if (!capable(CAP_SETUID)) {
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

origin.patch
ifdef-struct-task_structsecurity.patch
implement-file-posix-capabilities.patch
capabilities-reset-current-pdeath_signal-when-increasing-capabilities.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to