From: "Andrew G. Morgan" <morgan@kernel.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: charles.kirsch@internet.lu, lkml <linux-kernel@vger.kernel.org>,
linux-security-module@vger.kernel.org,
Gerald Combs <gerald@wireshark.org>,
Gilbert Ramirez <gram@alumni.rice.edu>,
Guy Harris <guy@alum.mit.edu>
Subject: Re: Possible problem in linux file posix capabilities
Date: Sun, 17 Feb 2008 17:55:43 -0800 [thread overview]
Message-ID: <47B8E59F.5030004@kernel.org> (raw)
In-Reply-To: <20080218013943.GA17142@sergelap.austin.ibm.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Serge E. Hallyn wrote:
| Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
| ---
| security/commoncap.c | 2 +-
| 1 files changed, 1 insertions(+), 1 deletions(-)
|
| diff --git a/security/commoncap.c b/security/commoncap.c
| index 5aba826..bb0c095 100644
| --- a/security/commoncap.c
| +++ b/security/commoncap.c
| @@ -552,7 +552,7 @@ int cap_task_kill(struct task_struct *p, struct
siginfo *info,
| * allowed.
| * We must preserve legacy signal behavior in this case.
| */
| - if (p->euid == 0 && p->uid == current->uid)
| + if (p->uid == current->uid)
| return 0;
Signed-off-by: Andrew G. Morgan <morgan@kernel.org>
Cheers
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFHuOWf+bHCR3gb8jsRAr5jAKCQ9MTWW9VNKGbbhacygeI6G7kqTACcCMEP
hyz+xgh91wN3+6dcL72S85c=
=Fjd8
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-18 1:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-17 22:48 Possible problem in linux file posix capabilities Serge E. Hallyn
2008-02-18 1:20 ` Andrew G. Morgan
2008-02-18 1:39 ` Serge E. Hallyn
2008-02-18 1:55 ` Andrew G. Morgan [this message]
2008-02-18 5:17 ` Casey Schaufler
2008-02-18 13:44 ` Serge E. Hallyn
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=47B8E59F.5030004@kernel.org \
--to=morgan@kernel.org \
--cc=charles.kirsch@internet.lu \
--cc=gerald@wireshark.org \
--cc=gram@alumni.rice.edu \
--cc=guy@alum.mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--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