All of lore.kernel.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: Joshua Brindle <jbrindle@tresys.com>
Cc: "SELinux(NSA)" <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] independent with attribute declararion oeder for attachment
Date: Mon, 13 Jun 2005 00:58:01 +0900	[thread overview]
Message-ID: <42AC5B89.9080902@kaigai.gr.jp> (raw)
In-Reply-To: <42AC457C.6020805@tresys.com>

Hi Joshua, Thanks for your comments.

This patch does NOT mean implict declaration of attribute, ALL attributes
require explict declaration when it's used in any TE statements such as ALLOW.
I wrote this patch to resolve declaration ordering problem. The feature of
problem is different from ROLE statement does not has explicitly declaration
statement.

Currently, the declaration statement of attribute must be placed in forward
of where it is used by any TE statements and TYPE declaration.
After you apply this patch, the declaration statement of attribute must be
placed in forward or backward of where it is used.
So, we still require ATTRIBUTE statments for explict declaration.

We can always discover an attribute declaration per effective attribute
in policy sources.
(An attached attribute to type without declaration is ignored.)
Does the declaration order in the policy source have a significant effect
for Tresys's loadable policy module ?

Thanks,

>>The following actions are same as current checkpolicy.
>>* ALLOW and any TE statements with undeclared attributes are restricted.
>>* Duplicate attribute declaration is restricted.
>>
>>* Any attribute need a declaration by ATTRIBUTE statement.
>>
> 
> It is undesirable to implicitly declare symbols by using them. In fact
> with the loadable policy modules this becomes problematic since we have
> to keep track of all dependancy information. For example, since roles
> are declared implicitly when assigned a type it isn't possible to
> discern declaring a role from using a role. In a module using a role
> should always have a dependancy on the role but declaring it wouldn't.
> This is something we are trying to solve but adding more implictly
> declared symbols would only make it harder.
> 
> Joshua Brindle

--
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.

  reply	other threads:[~2005-06-12 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-12 11:59 [PATCH] independent with attribute declararion oeder for attachment KaiGai Kohei
2005-06-12 14:23 ` Joshua Brindle
2005-06-12 15:58   ` KaiGai Kohei [this message]
2005-06-13 14:07 ` Stephen Smalley
2005-06-14 14:37   ` Interface between applications. (Re: [PATCH] independent with attribute declararion oeder for attachment) KaiGai Kohei

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=42AC5B89.9080902@kaigai.gr.jp \
    --to=kaigai@kaigai.gr.jp \
    --cc=SELinux@tycho.nsa.gov \
    --cc=jbrindle@tresys.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 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.