Re: How is the upstream SELinux refpolicy tied into Fedora?

David Sommerseth <[email protected]> Fri, 31 Mar 2023 14:49:48 +0000
Newsgroups gmane.linux.redhat.fedora.selinux
Message-ID <[email protected]>
On 31/03/2023 16:36, Neal Gompa wrote:
> On Fri, Mar 31, 2023 at 9:58 AM David Sommerseth <[email protected]> wrote:
>>
>>
>> Hi,
>>
>> I had an upstream SELinux pull-request merged in autumn 2020 [1].  But I
>> still don't see this SELinux boolean flag (renamed [2] to
>> "dbus_pass_tuntap_fd") present in Fedora 38.  So I wonder how the
>> SELinux refpolicy is consumed into Fedora's SELinux policies ... when
>> can I expect to see this in Fedora and RHEL SELinux policies?
>>
>> [1]
>> <https://github.com/SELinuxProject/refpolicy/commit/79c7859a4807236693c734421642d5aacff0a9e2>
>> [2]
>> <https://github.com/SELinuxProject/refpolicy/commit/ba3818ebcc3a627bc331c61acf2df13d223452ea>
>>
> 
> It's not consumed by Fedora or openSUSE at all. Fedora and openSUSE
> follow this instead: https://github.com/fedora-selinux/selinux-policy
> 
> As far as I know, there has been no reconciliation between the two
> happening anytime in the recent past and it's unlikely to happen
> anytime soon.
Maybe not the right place to ask ... but what is the purpose and goal of 
the SELinux refpolicy project if several of the larger Linux 
distributions doesn't pay attention to it?

I kinda would expect that lots of the SELinux policy details in Fedora 
would be pretty much the same challenges in other distributions as well.


-- 
kind regards,

David Sommerseth
OpenVPN Inc

_______________________________________________
selinux mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
signature.asc (application/pgp-signature, 855 B)
-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsFzBAEBCAAnBQJkJvMLCZBTlzn2TPwK3RYhBIIvMc1tEJTA+m/9n1OXOfZM
/ArdAAAG7Q//W8/cddV+tWM1RQjLuO3+2d5R5yzOaiBbyls0Lt7WjJhNiLkK
Y3l/XNNfbFjVVTuTPWBGgEYDjLVHVKDFNTtM1CcOnLF5gXfIqRHUaB4otw89
jDCZB3OEenirWpzAAlsTFE1stvCC4qfCfnNbWf4RADFt4FtceCDJbpxerRYM
dt/UzWBVwVA723yYD2WwPcd8jDcEsjQXF6yxU1Ze1QQGLXQfO6UJ4K766EmV
RlZrhEjg62C2Hc3tB0ifswBWSxk8NnN5+Nt7N4MTW4JG6S5+n58d+hhUzbWj
obyp3DWpWD9JIdTEXpcxFGx+8MhQMHm7APAdA97pDuL8xcSefWimotTobgoN
RFiWBYP1WCK5khva5dbI9+TPe4/Z1rkw7QjMLxca3zsuOhCxK+R1uaMnRHZ5
PDVHBxaKkMKFuUkjJzRkQ7T9HtzrwIQAGYW5MyNgG78kXo/plf6cgLRNSFG+
ALB83S18WQnZJHQEB1Vfm5nlY4N3gUnpsYAA75ZZp6AjePQ5VfpURM34SrEn
sfeRvV/P/uF0gZuZy3XPHhbXEnjqnNUENyFlrCFv69UIPf65Gtzcu2TmG23f
5Mt+I1rfgYzSBo9Sh/4OVBR01ABpGDlPKuxpqodC3i2ebkU4sB/AfjRcFHn6
DoeCQAqhEn+WG2+7pyfH2IPZWmGFlQxeCQc=
=Qd4q
-----END PGP SIGNATURE-----