| 1 |
On Thu, Nov 24, 2016 at 03:29:54PM +0000, Robert Sharp wrote: |
| 2 |
> On 23/11/16 17:30, Jason Zaman wrote: |
| 3 |
> > On Wed, Nov 23, 2016 at 05:20:59PM +0000, Robert Sharp wrote: |
| 4 |
> >> On 23/11/16 16:59, Robert Sharp wrote: |
| 5 |
> >>> On 23/11/16 15:58, Jason Zaman wrote: |
| 6 |
> >>>> Either is fine, but im probably just gonna stabilize the 2.6 userspace |
| 7 |
> >>>> in a couple weeks so that one is likely easier. and setools4 is waaay |
| 8 |
> >>>> better than 3. The important point is that you dont want to have both |
| 9 |
> >>>> policy.29 and policy.30 around. Then you get weirdness like if you |
| 10 |
> >>>> downgrade a kernel or something random it'll load in the old policy |
| 11 |
> >>>> which probably doesnt work properly, so whichever you pick, make sure |
| 12 |
> >>>> you nuke the other one. and semodule -B will rebuild the whole policy |
| 13 |
> >>>> again and load it. |
| 14 |
> >>> OK - I will go with policy.30 and add the keywords etc. I did a couple |
| 15 |
> >>> of local policy changes that may not be needed so will they disappear |
| 16 |
> >>> in all of this or do I need to remove them somehow first? |
| 17 |
> >>> |
| 18 |
> >>> Thanks for all your help, |
| 19 |
> >>> Robert |
| 20 |
> >>> |
| 21 |
> >> Sorry - noticed a couple of things while preping the emerge: |
| 22 |
> >> |
| 23 |
> >> 1) selinux-base-policy is blocking policycoreutils so presumably I need |
| 24 |
> >> to add that to my accept_keywords? |
| 25 |
> >> 2) this package has the "unconfined" use flag set but I don't use |
| 26 |
> >> unconfined. Does that matter? |
| 27 |
> > Oh, yeah the 2.6 userland needs at minimum 2.20151208-r6. Its been long |
| 28 |
> > enough, i'll stabilize the new policies right away so just wait a bit |
| 29 |
> > any sync again. |
| 30 |
> > |
| 31 |
> > unconfined useflag just builds it, if you are using strict you can turn |
| 32 |
> > off unconfined and set this in make.conf: |
| 33 |
> > POLICY_TYPES="strict" |
| 34 |
> > then it wont even build the targetted modules at all. |
| 35 |
> > |
| 36 |
> Thanks Jason - you have been busy. I have just updated to 20151208-r6 |
| 37 |
> and when I run semodule -B I get this message: |
| 38 |
> |
| 39 |
> "libsemanage.add_user: user system_u not in password file" |
| 40 |
|
| 41 |
That warning is harmless, i'll remove the line from the policy later. |
| 42 |
for now ignore it or manually remove the line to silence the warning. |
| 43 |
http://blog.perfinion.com/2016/10/selinux-userspace-26-released/ |
| 44 |
|
| 45 |
> |
| 46 |
> Googling suggests this was a problem in Fedora (see bug |
| 47 |
> https://bugzilla.redhat.com/show_bug.cgi?id=1378204) and it was fixed a |
| 48 |
> few days ago in their selinux-policy-3.13.1-191.20.fc24. I ran sesearch |
| 49 |
> as before and it comes up with the same results as before so I assume |
| 50 |
> the semodule command did not do what it was supposed to do. Is there a |
| 51 |
> work around for this or should I go ~arch on the policy as well? If so, |
| 52 |
> is there a way to avoid listing all the policy packages in my |
| 53 |
> accept_keywords file? |
| 54 |
> |
| 55 |
> Thanks again, |
| 56 |
> Robert |
| 57 |
> |
Archives