How is the upstream SELinux refpolicy tied into Fedora?

David Sommerseth <[email protected]> Fri, 31 Mar 2023 13:58:31 +0000

Newsgroups	gmane.linux.redhat.fedora.selinux
Message-ID	<[email protected]>

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>


--
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)