From: Daniel J Walsh <dwalsh@redhat.com>
To: SE Linux <selinux@tycho.nsa.gov>
Subject: upstart/SELinux problem loading the wrong policy with kernel version change
Date: Mon, 07 Apr 2008 21:31:59 -0400 [thread overview]
Message-ID: <47FACB0F.5050208@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you have a kernel that supports policy.21 and a tool chain that
supports policy.22 newer versions of policy and semanage changes will
update policy.22. However if there is a policy.21 around upstart will
load this on a reboot. (I guess init would have done the same.)
If the policy.21 does not exist libselinux will grab the highest policy
version and try to load it.
This is causing unlabeled_t files to be showing up. Basically if I
install a new policy with a new type, and then assign the context to a
file, the next reboot will cause the file to be labeled unlabeled_t.
I suggest that we either remove policy versioning all together, or
change libselinux to default to loading the highest policy version.
Either way the current loading of policy is broken.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkf6ywoACgkQrlYvE4MpobPKuwCePdHBoGYI13pVvugI/B9veFGo
88UAoKjr7Dp5gIaVW91rfbxgJQhngLCZ
=sAa6
-----END PGP SIGNATURE-----
--
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 reply other threads:[~2008-04-08 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 1:31 Daniel J Walsh [this message]
2008-04-08 12:54 ` upstart/SELinux problem loading the wrong policy with kernel version change Stephen Smalley
2008-04-08 13:29 ` Stephen Smalley
2008-04-18 14:32 ` 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=47FACB0F.5050208@redhat.com \
--to=dwalsh@redhat.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.