Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Package synce4l has been added to RHEL 9.0.0

Various security standards (e. g. CIS Server Level 2 benchmark) and scanners
(Openscap) request "Ensure no daemons are unconfined by SELinux".
To comply with this requirement, a security policy for your component needs to
be shipped either as part of selinux-policy package, or as a sub-package of
your component. If such a policy does not already exist, e. g. as a part of
your project upstream, it needs to be created in order for your package be
accepted into RHEL. Maintaining the selinux subpackage of the component takes
the advantage of having the package enhancements and its SELinux support
synchronized in time. Please follow the instructions in
https://fedoraproject.org/wiki/SELinux/IndependentPolicy
and make necessary changes to make the content of the package SELinux confined.

A SELinux policy workshop [2] [3] is available on github as an additional resource.
You can look for additional help on the #selinux internal IRC channel or via the
selinux-policy-owner email.

[1] https://fedoraproject.org/wiki/SELinux/IndependentPolicy
[2] https://github.com/RedHatGov/redhatgov.github.io
[3] https://github.com/RedHatGov/redhatgov.workshops