From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Jacques Thomas <jthomas@cs.purdue.edu>,
SE Linux <selinux@tycho.nsa.gov>,
method@manicmethod.com
Subject: Re: [PATCH 1/2] selinux: remove dead code in type_attribute_bounds_av()
Date: Thu, 21 Jan 2010 15:00:15 +0900 [thread overview]
Message-ID: <4B57ED6F.6040803@ak.jp.nec.com> (raw)
In-Reply-To: <1263994416.24133.4.camel@moss-pluto.epoch.ncsc.mil>
(2010/01/20 22:33), Stephen Smalley wrote:
> $ make C=2 security/selinux/ss/services.o
> security/selinux/ss/services.c: In function ‘type_attribute_bounds_av’:
> security/selinux/ss/services.c:524: warning: unused variable ‘target’
> security/selinux/ss/services.c:520: warning: unused variable ‘lo_tcontext’
Sorry, it was fixed.
--------
This patch removes dead code in type_attribute_bounds_av().
Due to the historical reason, the type boundary feature is delivered
from hierarchical types in libsepol, it has supported boundary features
both of subject type (domain; in most cases) and target type.
However, we don't have any actual use cases in bounded target types,
and it tended to make conceptual confusion.
So, this patch removes the dead code to apply boundary checks on the
target types. I makes clear the TYPEBOUNDS restricts privileges of
a certain domain bounded to any other domain.
Signed-off-by: KaiGai Kohei <kaigai@ak.jp.nec.com>
--
security/selinux/ss/services.c | 43 +++------------------------------------
1 files changed, 4 insertions(+), 39 deletions(-)
diff --git a/security/selinux/ss/services.c b/security/selinux/ss/services.c
index 3b42b15..4a2bf21 100644
--- a/security/selinux/ss/services.c
+++ b/security/selinux/ss/services.c
@@ -516,16 +516,14 @@ static void type_attribute_bounds_av(struct context *scontext,
u16 tclass,
struct av_decision *avd)
{
- struct context lo_scontext;
- struct context lo_tcontext;
- struct av_decision lo_avd;
struct type_datum *source
= policydb.type_val_to_struct[scontext->type - 1];
- struct type_datum *target
- = policydb.type_val_to_struct[tcontext->type - 1];
- u32 masked = 0;
if (source->bounds) {
+ struct context lo_scontext;
+ struct av_decision lo_avd;
+ u32 masked;
+
memset(&lo_avd, 0, sizeof(lo_avd));
memcpy(&lo_scontext, scontext, sizeof(lo_scontext));
@@ -538,40 +536,7 @@ static void type_attribute_bounds_av(struct context *scontext,
if ((lo_avd.allowed & avd->allowed) == avd->allowed)
return; /* no masked permission */
masked = ~lo_avd.allowed & avd->allowed;
- }
-
- if (target->bounds) {
- memset(&lo_avd, 0, sizeof(lo_avd));
-
- memcpy(&lo_tcontext, tcontext, sizeof(lo_tcontext));
- lo_tcontext.type = target->bounds;
-
- context_struct_compute_av(scontext,
- &lo_tcontext,
- tclass,
- &lo_avd);
- if ((lo_avd.allowed & avd->allowed) == avd->allowed)
- return; /* no masked permission */
- masked = ~lo_avd.allowed & avd->allowed;
- }
-
- if (source->bounds && target->bounds) {
- memset(&lo_avd, 0, sizeof(lo_avd));
- /*
- * lo_scontext and lo_tcontext are already
- * set up.
- */
-
- context_struct_compute_av(&lo_scontext,
- &lo_tcontext,
- tclass,
- &lo_avd);
- if ((lo_avd.allowed & avd->allowed) == avd->allowed)
- return; /* no masked permission */
- masked = ~lo_avd.allowed & avd->allowed;
- }
- if (masked) {
/* mask violated permissions */
avd->allowed &= ~masked;
--
OSS Platform Development Division, NEC
KaiGai Kohei <kaigai@ak.jp.nec.com>
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-01-21 6:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 19:24 Type boundaries: questions on the semantics / is the enforcement correct ? Jacques Thomas
2009-11-18 2:44 ` KaiGai Kohei
2009-11-19 16:07 ` Jacques Thomas
2009-11-30 18:40 ` Jacques Thomas
2009-12-01 1:02 ` KaiGai Kohei
2009-12-01 3:53 ` Jacques Thomas
2009-12-08 19:46 ` Joshua Brindle
2010-01-15 15:51 ` Stephen Smalley
2010-01-18 10:10 ` KaiGai Kohei
2010-01-20 4:25 ` [PATCH 1/2] selinux: remove dead code in type_attribute_bounds_av() KaiGai Kohei
2010-01-20 13:33 ` Stephen Smalley
2010-01-20 16:29 ` contents of /etc/selinux/<type>/contexts/users/* Hasan Rezaul-CHR010
2010-01-20 17:33 ` Stephen Smalley
2010-01-21 6:00 ` KaiGai Kohei [this message]
2010-01-21 14:08 ` [PATCH 1/2] selinux: remove dead code in type_attribute_bounds_av() Stephen Smalley
2010-01-24 22:24 ` James Morris
2010-01-20 4:26 ` [PATCH 2/2] libsepol: remove dead code in check_avtab_hierarchy_callback() KaiGai Kohei
2010-02-05 5:42 ` KaiGai Kohei
2010-02-05 14:50 ` Stephen Smalley
2010-02-09 6:46 ` KaiGai Kohei
2010-02-16 2:36 ` KaiGai Kohei
2010-02-16 15:25 ` Stephen Smalley
2010-02-16 23:49 ` KaiGai Kohei
2010-02-17 13:51 ` Stephen Smalley
2010-02-19 7:33 ` KaiGai Kohei
2010-02-19 15:20 ` Stephen Smalley
2010-03-01 2:43 ` KaiGai Kohei
2010-03-01 14:34 ` Stephen Smalley
2010-03-03 8:09 ` KaiGai Kohei
2010-03-04 16:01 ` Joshua Brindle
2010-03-04 16:24 ` Joshua Brindle
2010-03-05 0:39 ` KaiGai Kohei
2010-03-05 14:19 ` Joshua Brindle
2010-03-05 14:25 ` Stephen Smalley
2010-03-05 14:31 ` Joshua Brindle
2010-03-08 6:56 ` KaiGai Kohei
2010-03-08 15:27 ` Joshua Brindle
2010-02-19 17:31 ` Stephen Smalley
2010-02-21 22:09 ` James Morris
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=4B57ED6F.6040803@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=jthomas@cs.purdue.edu \
--cc=method@manicmethod.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.