From: Joshua Brindle <jbrindle@tresys.com>
To: KaiGai Kohei <kaigai@kaigai.gr.jp>
Cc: "SELinux(NSA)" <SELinux@tycho.nsa.gov>
Subject: Re: [PATCH] independent with attribute declararion oeder for attachment
Date: Sun, 12 Jun 2005 10:23:56 -0400 [thread overview]
Message-ID: <42AC457C.6020805@tresys.com> (raw)
In-Reply-To: <42AC23B6.8070304@kaigai.gr.jp>
KaiGai Kohei wrote:
><snip>
>
>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.
next prev parent reply other threads:[~2005-06-12 14:23 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 [this message]
2005-06-12 15:58 ` KaiGai Kohei
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=42AC457C.6020805@tresys.com \
--to=jbrindle@tresys.com \
--cc=SELinux@tycho.nsa.gov \
--cc=kaigai@kaigai.gr.jp \
/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.