analysing optional policy

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

 



I'm having a problem with optional policy not being used when I think it 
should.

Is it possible to use apol to get information on optional policy for .pp files 
so I can try to work out why it doesn't get enabled?

                unconfined_run_to(depmod_t, depmod_exec_t)

In the Debian policy I have the above in an optional section of base.pp but 
for reasons that I don't understand it's not being loaded (both tests and 
running apol on policy.24 show this).

I've inspected the contents of base.conf and they appear to be OK.

Any suggestions of other tools to analyse this will be appreciated.

-- 
russell@xxxxxxxxxxxx
http://etbe.coker.com.au/          My Main Blog
http://doc.coker.com.au/           My Documents Blog


--
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