From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: does load_policy default to loading the lowest polvers available?
Date: Wed, 14 Oct 2015 15:34:11 +0200 [thread overview]
Message-ID: <20151014133408.GA5222@x250> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
I had some issue that just confused me (to say the least) It seems that
I have now solved this.
There were two policy.X files in my /etc/selinux/SELINUXTYPE/policy dir,
on 29 an one 30. The 29 seemingly had a bug in it.
It seems that load_policy (or its libselinux equivalent) defaults to
the lowest policy available (29 instead of 30 in this case)
Why is that?
I fixed the issue by removing the policy.29 file (i think at least)
- --
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
https://sks-keyservers.net/pks/lookup?op=get&search=0x314883A202DFF788
Dominick Grift
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQGcBAEBCgAGBQJWHlnMAAoJENAR6kfG5xmc0IsL+gPvY2hmVUW/77tfYW4ruSJS
F29xdIZiFh/70Nv10T8rWmyY/8YzMELucGMg8117FeFUe0V8YRdBtkOYDwCDrZLh
9uAs3Jrnfa109XxE5PQGAgqIZtfAFTKSpNylDoQPg6kcFWCo1nna3EjgaIC8KuW7
FxpWv/27DtequhIjgwNiW2jhzBhwmfKlCSa1BryRzecoboIz7ApDqdiGQAeNCc8i
I+x6MXZ8P/F2K1aTutJhzjmOUR+7Oy+0il9wtdxGwEbD+GrVLLFBXi5/k9/pNyVX
+hwQTTputG1SJ3JAX3/mFa7OmDvdADxWBXvcw7yWLD6moO3nMcW76QiphbNFu1aF
Vtu037e+TnbQGMqSi2sFllzlGXR9MmWeKcDcF5Nl0P4pVmDbuFcvBcYmlR6VfAqE
fpooQinx130pLHe2vVQqfdPChIlT6wmTX7uPO9/ax16xWrZYjY2bZqaycI5uYCV9
RZIdWUCF+i5JiNKoNjQkJVCI3hdzEoM5aI9iZ3H3MA==
=CMCd
-----END PGP SIGNATURE-----
next reply other threads:[~2015-10-14 13:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 13:34 Dominick Grift [this message]
2015-10-14 13:56 ` does load_policy default to loading the lowest polvers available? Stephen Smalley
2015-10-14 14:11 ` Dominick Grift
2015-10-14 14:17 ` Stephen Smalley
2015-10-14 14:29 ` Dominick Grift
2015-10-14 15:44 ` Stephen Smalley
2015-10-14 15:48 ` Dominick Grift
2015-10-14 16:05 ` Stephen Smalley
2015-10-14 16:26 ` Dominick Grift
2015-10-14 16:41 ` Dominick Grift
2015-10-14 16:53 ` Stephen Smalley
2015-10-14 17:34 ` Dominick Grift
2015-10-14 17:38 ` Dominick Grift
2015-10-14 17:40 ` Stephen Smalley
2015-10-14 17:51 ` Dominick Grift
2015-10-14 18:07 ` Dominick Grift
2015-10-14 20:30 ` Christopher J. PeBenito
2015-10-14 20:34 ` Dominick Grift
2015-10-15 11:58 ` Richard Haines
2015-10-15 12:08 ` Dominick Grift
2015-10-14 18:52 ` Stephen Smalley
-- strict thread matches above, loose matches on Subject: below --
2015-11-26 16:51 Dominick Grift
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=20151014133408.GA5222@x250 \
--to=dac.override@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.