Re: Enabling policy capabilities

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

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephen Smalley wrote:
> Where do we stand on actually enabling policy capabilities in policy so
> that people can start using newer features that depend on them?
> 
> I've definitely seen patches adding permissions for the peer checks, so
> is there anything preventing us from trying to enable
> network_peer_controls in policy and seeing what breaks (after Fedora 9
> at this point, I suppose - unfortunate that we didn't enable it sooner)?
> 
> I haven't seen patches adding permissions for open other than just to
> define them, IIRC.  So enabling open_perms would be rather bad right now
> except for unconfined domains.  As a possible strategy for gradual
> roll-out of open perm, we could add open everywhere there is a read or
> write granted, enable the open_perms capability, verify no breakage, and
> then gradually remove open permission where we know it to be unneeded.
> 
Open checks will be added in Fedora 10, along with turning on Xace.  We
are frozen in Fedora 9.  No new functionality.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkf+OlIACgkQrlYvE4MpobM+4gCcCHxrHzMnej50qajUUFTqMU3j
BMcAn3JWNm2zr6nl6QiyqZbWwfLSjQx1
=bMXX
-----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@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