Bug 2143153 - Change wording in /etc/selinux/config
Summary: Change wording in /etc/selinux/config
Keywords:
Status: VERIFIED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: selinux-policy
Version: 9.1
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Nikola Knazekova
QA Contact: Milos Malik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-16 08:23 UTC by Renaud Métrich
Modified: 2023-08-16 06:42 UTC (History)
4 users (show)

Fixed In Version: selinux-policy-38.1.20-1.el9
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-139535 0 None None None 2022-11-16 08:29:29 UTC

Description Renaud Métrich 2022-11-16 08:23:02 UTC
Description of problem:

The /etc/selinux/config file, which is created by postinstall of selinux-policy package, mentions Fedora and a Fedora doc:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# See also:
# https://docs.fedoraproject.org/en-US/quick-docs/getting-started-with-selinux/#getting-started-with-selinux-selinux-states-and-modes
#
# NOTE: In earlier Fedora kernel builds, SELINUX=disabled would also
# fully disable SELinux during boot. If you need a system with SELinux
...
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

IMHO it would be better to remove "In earlier Fedora kernel builds" and replace this by "Up to RHEL 8 release included,".

Additionally the doc link to fedoraproject should be replaced by a doc link to RHEL9 below:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/using_selinux/changing-selinux-states-and-modes_using-selinux#changing-selinux-modes-at-boot-time_changing-selinux-states-and-modes

Version-Release number of selected component (if applicable):

selinux-policy

How reproducible:

N/A


Note You need to log in before you can comment on or make changes to this bug.