On Tue, 2014-04-22 at 22:44 +0200, Dominick Grift wrote: > On Tue, 2014-04-22 at 22:39 +0200, Dominick Grift wrote: > > On Tue, 2014-04-22 at 15:44 -0400, Steve Lawrence wrote: > > > > > >>> Also, i still have that weird boolean issue where, even though sesearch > > > >>> shows the rules are loaded and enabled, SELinux still blocks the access > > > >> > > > >> I think we actually fixed this about an hour ago. Give it a shot, let us > > > >> know if it's actually fixed. > > > > > > > > Nice, i will try with up-to-date secilc tomorrow > > > > Current head does not fix the boolean issue, i just verified and the > > issue is still there > > Actually it partly works (but it did before as well) > > Its the conditional capability permissions that do not work > > i have for example a set of consitional rules: > > (allow ARG1 security_t (security load_policy)) > (allow ARG1 security_t (file (write))) > > The file write works but the security load_policy does not work > The latest commit seems to have fixed the conditional issue at long last, thaanks!! _______________________________________________ Selinux mailing list Selinux@xxxxxxxxxxxxx To unsubscribe, send email to Selinux-leave@xxxxxxxxxxxxx. To get help, send an email containing "help" to Selinux-request@xxxxxxxxxxxxx.
