[DSE-Dev] Bug#829617: Bug#829617: selinux-policy-default not available for stable

Russell Coker russell at coker.com.au
Mon Jul 11 02:12:22 UTC 2016


We can backport the POLICY from the latest refpolicy package with the hooks for the versions of the tools in Jessie.

What's the procedure for getting this done? I can easily build the package in question as I have it running on all my own servers.

On 5 July 2016 7:24:45 PM AEST, Laurent Bigonville <bigon at debian.org> wrote:
>severity 829617 wishlist
>tag 829617 + jessie
>thanks
>
>Le 04/07/16 à 20:37, Klaus Ethgen a écrit :
>> selinux-policy-default is not available for stable (jessie) than only
>> for old-stable and testing (and unstable).
>
>Yes the policy was considered too buggy when stable has been released 
>and thus has been removed.
>
>We could backport the refpolicy currently in testing, but we might need
>
>to backport the userspace as well as they changed the way the policy
>was 
>loaded.
>
>
>> Without this policy, all selinux tools and kernel support makes no
>sense
>> at all. (True, I can compile my own policy but this is fare behind a
>> casual admin.)
>
>TBH, even with a policy in the archive, I think it would require 
>adjustment from the administrator anyway
>
>>
>> So please provide that policy again.
>>
>> See also [0].
>>
>> [0] https://wiki.debian.org/SELinux/Setup#Steps_to_setup_SELinux
>
>_______________________________________________
>SELinux-devel mailing list
>SELinux-devel at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/selinux-devel

-- 
Sent from my Nexus 6P with K-9 Mail.



More information about the SELinux-devel mailing list