From: Stephen Smalley <sds@tycho.nsa.gov>
To: Divya Vyas <dvyas@mvista.com>, selinux <selinux@tycho.nsa.gov>
Subject: Re: Can I change default policy from targeted to minimum
Date: Fri, 11 Sep 2015 13:11:59 -0400 [thread overview]
Message-ID: <55F30B5F.5080203@tycho.nsa.gov> (raw)
In-Reply-To: <CA+=dQ-_fxDCjHZmO39O9=S0eQpWN7fhpQQRyqv9d-f82zXahdA@mail.gmail.com>
On 09/11/2015 12:43 PM, Divya Vyas wrote:
> Hi Dominick,
>
> I have a question, What is role of policy.29/28/27 . If I understand
> correctly It is a binary policy called while kernel booting. Is is
> symbolic lick with policy.kern.
The suffix indicates the policy format version; the version number is
also contained within the file header but having it as a file name
suffix is convenient for supporting multiple versions on the same system
(e.g. for booting different kernels) and for allowing userspace to
select the right file without having to parse it.
It isn't normally just a symlink.
In Android, we dispensed with the policy version suffix and just called
it "sepolicy" because we could ensure that the kernel and userspace were
aligned and that the policy file would always be compatible with the
kernel. We also had to move it out of /etc and into / so that it could
be loaded before the /system partition was mounted, since /etc in
Android is just a symlink to /system/etc and is not available immediately.
next prev parent reply other threads:[~2015-09-11 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 11:55 Can I change default policy from targeted to minimum Divya Vyas
2015-09-11 13:41 ` Dominick Grift
2015-09-11 15:45 ` Divya Vyas
2015-09-11 15:53 ` Dominick Grift
2015-09-11 16:43 ` Divya Vyas
2015-09-11 16:51 ` Dominick Grift
2015-09-11 17:11 ` Stephen Smalley [this message]
2015-09-18 23:30 ` how to run setsebool -P in chroot? Bond Masuda
2015-09-20 21:13 ` Paul Moore
2015-09-21 20:12 ` Stephen Smalley
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=55F30B5F.5080203@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=dvyas@mvista.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.