From: lvrabec@redhat.com (Lukas Vrabec)
Date: Fri, 9 Mar 2018 10:16:35 +0100
Subject: [refpolicy] Rebasing fedora selinux-policy with refpolicy upstream
Message-ID: <8aaf5b27-9bb7-ae2e-4864-44cfef01d48e@redhat.com>
To: refpolicy@oss.tresys.com
List-Id: refpolicy.oss.tresys.com

Hi All,

As a maintainer of SELinux distribution policy for Fedora, I would like
to start with rebasing SELinux modules with upstream refpolicy.

Unfortunately refpolicy and fedora selinux-policy quite diverged
during the time. Do the full rebase will be probably really messy
action. I prefer start with smaller modules from contrib branch/repo.

However I have few questions here. SELinux policy in Fedora cover more
setups then refpolicy (contain more allow/generic rules). I'll merge
allow rules from refpolicy which are missing in Fedora selinux-policy,
but would you like to see allow rules from fedora selinux-policy in
refpolicy upstream? Lot of these rules could be Fedora/RHEL specific.
Should I start sending patches and you will decide which
should be merged?

Thanks,
Lukas.

-- 
Lukas Vrabec
Software Engineer, Security Technologies
Red Hat, Inc.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20180309/2bf3bfc9/attachment.bin