From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stefan Schulze Frielinghaus <stefan@sf-net.com>
Cc: SELinux List <selinux@tycho.nsa.gov>
Subject: Re: tunable and if-else conditional
Date: Wed, 05 Sep 2007 17:21:27 +0000 [thread overview]
Message-ID: <1189012887.30065.31.camel@gorn> (raw)
In-Reply-To: <6E78FE11-FAA3-4C3B-A87E-FA60ABB71863@sf-net.com>
On Wed, 2007-09-05 at 17:35 +0200, Stefan Schulze Frielinghaus wrote:
> reading an older poste (http://www.nsa.gov/selinux/list-archive/0610/
> thread_body16.cfm) I wonder about the difference between tunable and
> an if-else conditional.
>
> <quote>
> Tunable_policy are blocks that will be replaced by a similar language
> feature when it becomes available. Tunables will be similar to
> conditionals, except they will be selected during the policy module
> linking instead of being selectable at runtime.
> </quote>
>
> Using the latest stable refpolicy (20070629) the feature has already
> changed? I would guess so because I can change the booleans via
> setsebool at runtime.
No, true tunables require support in the toolchain. That won't happen
until after the new policy representation is completed.
> Looking at the file "loadable_module.spt" the tunable seems to me
> exact the same like a if-else conditional. But I'm not a M4 guy and
> wanted to make sure. Is this right that a tunable and a if-else
> conditional is the same now?
Tunables are implemented as conditional policy right now.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
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:[~2007-09-05 17:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-05 15:35 tunable and if-else conditional Stefan Schulze Frielinghaus
2007-09-05 17:21 ` Christopher J. PeBenito [this message]
2007-09-06 6:18 ` Stefan Schulze Frielinghaus
2007-09-06 12:39 ` Christopher J. PeBenito
2007-09-06 13:40 ` Stefan Schulze Frielinghaus
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=1189012887.30065.31.camel@gorn \
--to=cpebenito@tresys.com \
--cc=selinux@tycho.nsa.gov \
--cc=stefan@sf-net.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.