This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2178950 - setroubleshootd can fail when SELinux is disabled
Summary: setroubleshootd can fail when SELinux is disabled
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: setroubleshoot
Version: 8.7
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Vit Mojzis
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-16 09:23 UTC by Renaud Métrich
Modified: 2023-09-19 17:46 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-19 17:46:59 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-5203 0 None Migrated None 2023-09-19 17:44:11 UTC
Red Hat Issue Tracker RHELPLAN-152029 0 None None None 2023-03-16 09:23:54 UTC
Red Hat Knowledge Base (Solution) 7003350 0 None None None 2023-03-20 09:35:27 UTC

Description Renaud Métrich 2023-03-16 09:23:25 UTC 
Description of problem:

When SELinux is disabled (either in /etc/selinux/config or on kernel command line "selinux=0"), it's still possible for setroubleshootd service to start, which leads to a failure:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Mar 16 10:11:21 vm-rhel8 systemd[1]: Starting SETroubleshoot daemon for processing new SELinux denial logs...
Mar 16 10:11:22 vm-rhel8 setroubleshoot[2046]: SELinux not enabled, setroubleshootd exiting...
Mar 16 10:11:22 vm-rhel8 systemd[1]: setroubleshootd.service: Main process exited, code=exited, status=3/NOTIMPLEMENT>
Mar 16 10:11:22 vm-rhel8 systemd[1]: setroubleshootd.service: Failed with result 'exit-code'.
Mar 16 10:11:22 vm-rhel8 systemd[1]: Failed to start SETroubleshoot daemon for processing new SELinux denial logs.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

Especially, this happens in two cases:

1. if the user starts the service through command line

   # systemctl start setroubleshootd

2. when "sealert" is started, e.g. by insights-client

   # sealert -l "*"

I think we need to harden the service to avoid these two cases.
For this, I'm proposing to add the following stanzas:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
ConditionSecurity=selinux
RefuseManualStart=yes
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

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

setroubleshoot-server-3.3.26-5.el8.x86_64

How reproducible:

Always

Steps to Reproduce:
1. Boot with "selinux=0"
2. Trigger startup using `sealert -l "*"` command

Actual results:

Failure

Expected results:

No failure

Additional info:

Additionally it would be nice to avoid `sealert` from falling in timeout when setroubleshootd cannot start (e.g. because ConditionSecurity=selinux was added).
For now it waits too long before failing:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
# sealert -l "*"
... 25 seconds later ...
Unable to establish connection to setroubleshoot daemon!
Check output of 'journalctl -t setroubleshoot' for more details.
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
Comment 6 RHEL Program Management 2023-09-19 17:41:55 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 7 RHEL Program Management 2023-09-19 17:46:59 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.