From: "Andrew G. Morgan" <morgan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Linux Security Modules List
<linux-security-module@vger.kernel.org>
Subject: Re: [PATCH] security: protect legacy apps from insufficient privilege
Date: Thu, 22 May 2008 06:19:08 -0700 [thread overview]
Message-ID: <483572CC.9060705@kernel.org> (raw)
In-Reply-To: <20080521224137.8d5c0089.akpm@linux-foundation.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andrew Morton wrote:
| With a judiciously placed `continue' we can do this:
|
| CAP_FOR_EACH_U32(i) {
| __u32 value_cpu;
|
| if (i >= tocopy) {
| /*
| * Legacy capability sets have no upper bits
| */
| bprm->cap_post_exec_permitted.cap[i] = 0;
| continue;
| }
| /*
| * pP' = (X & fP) | (pI & fI)
| */
| value_cpu = le32_to_cpu(caps->data[i].permitted);
| bprm->cap_post_exec_permitted.cap[i] =
| (current->cap_bset.cap[i] & value_cpu) |
| (current->cap_inheritable.cap[i] &
| le32_to_cpu(caps->data[i].inheritable));
| if (value_cpu & ~bprm->cap_post_exec_permitted.cap[i]) {
| /*
| * insufficient to execute correctly
| */
| ret = -EPERM;
| }
| }
|
| OK?
Yes.
Acked-by: Andrew G. Morgan <morgan@kernel.org>
Cheers
Andrew
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFINXLL+bHCR3gb8jsRAiGUAJ49d61n7+uhc3M5vJjT5398w9tRGgCgwLRe
vXHOIIJAoHvlGNACagKSPes=
=oPN0
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-05-22 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 15:50 [PATCH] security: protect legacy apps from insufficient privilege Andrew G. Morgan
2008-05-21 20:34 ` Serge E. Hallyn
2008-05-22 5:18 ` Andrew G. Morgan
2008-05-22 5:41 ` Andrew Morton
2008-05-22 13:19 ` Andrew G. Morgan [this message]
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=483572CC.9060705@kernel.org \
--to=morgan@kernel.org \
--cc=akpm@linux-foundation.org \
--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;
as well as URLs for NNTP newsgroup(s).