From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Calling typeattribute within a tunable_policy() is not allowed?
Date: Fri, 19 Aug 2011 08:04:46 -0400 [thread overview]
Message-ID: <4E4E515E.1050906@tresys.com> (raw)
In-Reply-To: <SNT139-W44584FA16D84E284D0FC22AB2A0@phx.gbl>
On 08/18/11 21:44, HarryCiao wrote:
>
>> > > I guess that attributes are not something that can be switched on/off
>> > > through a tunable.
>> >
>> > Just a side note, so far the tunable is implemented as boolean, and the
>> > tunable_policy macro is expanded as if-else conditionals by m4, aiming
>> > to define some block of rules that could be switched on/off at runtime.
>> > However, the tunable and tunable_policy should take effect at module
>> > link/expand time - if the tunable if off, then related block of rules
>> > would not be linked and expanded at all.
>>
>> Yes, that is the reason I created tunables. The toolchain just hasn't
>> implemented that support yet. CIL will have this support, but thats not
>> done yet.
>
> I just started to add such support for separating tunable from boolean
> in the toolchain, hope it would be useful for CIL as well.
I think its already been implemented in CIL. You should talk to Steve
Lawrence about it.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2011-08-19 12:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-13 21:06 [refpolicy] Calling typeattribute within a tunable_policy() is not allowed? Sven Vermeulen
2011-08-16 19:26 ` Christopher J. PeBenito
2011-08-17 3:39 ` Sven Vermeulen
2011-08-18 8:14 ` HarryCiao
2011-08-18 13:21 ` Christopher J. PeBenito
2011-08-19 1:44 ` HarryCiao
2011-08-19 12:04 ` Christopher J. PeBenito [this message]
2011-08-19 12:58 ` Steve Lawrence
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=4E4E515E.1050906@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.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.