RE: Update to docs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



There have been a couple times when I wanted to remove a rule from the system policy for a specific BSP.  So I guess I would vote for override if I need to choose one or the other.  But would it be reasonable to allow both overrides and concatenates ?  That would be my preference.

________________________________________
From: owner-selinux@xxxxxxxxxxxxx [owner-selinux@xxxxxxxxxxxxx] on behalf of Stephen Smalley [sds@xxxxxxxxxxxxx]
Sent: Friday, September 14, 2012 5:51 AM
To: William Roberts
Cc: selinux@xxxxxxxxxxxxx
Subject: Re: Update to docs

On Thu, 2012-09-13 at 16:58 -0700, William Roberts wrote:
> Can I get the documentation on the wiki updated under "SE Android
> policy" the second paragraph. I would like to update that you can
> specify genfs_context files and seapp_context files...maybe something
> like below will be sufficient:
>
> Device-specific additions for the policy configuration can be placed
> in a sepolicy.te file (for kernel TE policy rules), a sepolicy.fc file
> (for file_contexts entries), a sepolicy.pc file (for property_contexts
> entries), a sepolicy.genfs_contexts file (for genfs entries), or
> seapp_contexts (for seapp rule entries) under any of the
> target/board/<device>, device/<vendor>/<device>, or
> vendor/<vendor>/<device> directories. These files if present are
> merged into the policy during the build.

Updated.  However, this is starting to get unwieldy.  I was wondering
whether we should switch over to a model where we permit a sepolicy
subdirectory under the device directories that can contain any kind of
policy file (without requiring a sepolicy. prefix on each one since they
will be in a subdirectory).  Just need to decide how we would merge
multiple .te files with the same name, i.e. concatenate/union vs.
replace/override.

--
Stephen Smalley
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@xxxxxxxxxxxxx with
the words "unsubscribe selinux" without quotes as the message.


[Index of Archives]     [Selinux Refpolicy]     [Linux SGX]     [Fedora Users]     [Fedora Desktop]     [Yosemite Photos]     [Yosemite Camping]     [Yosemite Campsites]     [KDE Users]     [Gnome Users]

  Powered by Linux