From: Daniel J Walsh <dwalsh@redhat.com>
To: Elia Pinto <andronicus.spiros@gmail.com>
Cc: selinux@tycho.nsa.gov, refpolicy@oss1.tresys.com
Subject: Re: Policy file and Selinux Policy question
Date: Fri, 11 Sep 2009 10:25:32 -0400 [thread overview]
Message-ID: <4AAA5DDC.7060403@redhat.com> (raw)
In-Reply-To: <51af93b70909110541w1bef874h22931a6421388028@mail.gmail.com>
On 09/11/2009 08:41 AM, Elia Pinto wrote:
> In creating an selinux policy i can define the type of policy (strict,
> targeted, MLS and a custom : e,g make NAME=selinuxvariant -f
> /usr/share/selinux/devel/Makefile) to which the policy file has to be
> applied.
>
> But given a policy file (policy.pp) as it is possible to understand via
> some API interface at which policies the policy file relate ? In other
> words, it is redundant to have the information elsewhere on the type of
> policy to which the policy file you referring to? Also the information that
> the policy file is a base or loadable policy is in policy file ? If yes, how
> to inquiry via selinux API ?
>
> Thanks a lot in advance
>
I guess the question I would raise, is what is varying between the policies that you feel is necessary.
option_policy(
)
Should handle the case where an interface is different. The only case I currently know of where you migh vary is on
file context MLS Level.
--
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.
WARNING: multiple messages have this Message-ID (diff)
From: dwalsh@redhat.com (Daniel J Walsh)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Policy file and Selinux Policy question
Date: Fri, 11 Sep 2009 10:25:32 -0400 [thread overview]
Message-ID: <4AAA5DDC.7060403@redhat.com> (raw)
In-Reply-To: <51af93b70909110541w1bef874h22931a6421388028@mail.gmail.com>
On 09/11/2009 08:41 AM, Elia Pinto wrote:
> In creating an selinux policy i can define the type of policy (strict,
> targeted, MLS and a custom : e,g make NAME=selinuxvariant -f
> /usr/share/selinux/devel/Makefile) to which the policy file has to be
> applied.
>
> But given a policy file (policy.pp) as it is possible to understand via
> some API interface at which policies the policy file relate ? In other
> words, it is redundant to have the information elsewhere on the type of
> policy to which the policy file you referring to? Also the information that
> the policy file is a base or loadable policy is in policy file ? If yes, how
> to inquiry via selinux API ?
>
> Thanks a lot in advance
>
I guess the question I would raise, is what is varying between the policies that you feel is necessary.
option_policy(
)
Should handle the case where an interface is different. The only case I currently know of where you migh vary is on
file context MLS Level.
next prev parent reply other threads:[~2009-09-11 14:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 12:41 Policy file and Selinux Policy question Elia Pinto
2009-09-11 12:41 ` [refpolicy] " Elia Pinto
2009-09-11 14:25 ` Daniel J Walsh [this message]
2009-09-11 14:25 ` Daniel J Walsh
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=4AAA5DDC.7060403@redhat.com \
--to=dwalsh@redhat.com \
--cc=andronicus.spiros@gmail.com \
--cc=refpolicy@oss1.tresys.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.