From: dE <de.techno@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: What's a policy configuration file?
Date: Fri, 02 May 2014 12:00:55 +0530 [thread overview]
Message-ID: <53633B9F.7010307@gmail.com> (raw)
In-Reply-To: <1398966664.19535.20.camel@x220.localdomain>
On 05/01/14 23:21, Dominick Grift wrote:
> On Thu, 2014-05-01 at 22:58 +0530, dE wrote:
>
>> http://www.nsa.gov/research/_files/selinux/papers/policy2/x109.shtml
>>
>> http://selinuxproject.org/page/ConfigurationFiles#Policy_Configuration_Files
>>
>> I would like to know what the official website means -- it's definitely
>> the sources. I hope I'll read about policy.conf in the NSA reference.
> I suppose it can have various meanings depending on the context in which
> the term is used.
>
> Policy IS configuration, and so any file with policy in it in any format
> could be referred to as "policy configuration" file
>
> Then there are the configuration files that are distributed with the
> policy configuration. I suppose technically those are "policy
> configuration" configuration files.
>
> There there is often also a configuration files that specifies the
> options with which a policy configuration is compiled, and so i suppose
> one could also refer to that file as a "policy configuration"
> configuration file.
>
> Welcome to the wonderful world of SELinux terminology!
>
I've never read about the config in para 3.
As of the termionogy -- I'm sure the policy source file should be called
policy source not 'policy config' for the same reason as C/C++ source
files are called the source.
prev parent reply other threads:[~2014-05-02 6:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 16:55 What's a policy configuration file? dE
2014-05-01 17:11 ` Stephen Smalley
2014-05-01 17:28 ` dE
2014-05-01 17:45 ` Stephen Smalley
2014-05-02 6:24 ` dE
2014-05-01 17:51 ` Dominick Grift
2014-05-02 6:30 ` dE [this message]
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=53633B9F.7010307@gmail.com \
--to=de.techno@gmail.com \
--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.