Bug 2196807

Summary:	Systemd-analyze security reports false information
Product:	Red Hat Enterprise Linux 8	Reporter:	Attila Lakatos <alakatos>
Component:	systemd	Assignee:	David Tardon <dtardon>
Status:	CLOSED MIGRATED	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.9	CC:	dtardon, jamacku, systemd-maint-list
Target Milestone:	rc	Keywords:	Bugfix, MigratedToJIRA, Triaged
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-21 12:34:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Attila Lakatos 2023-05-10 09:46:35 UTC

Description of problem:
The output of 'systemd-analyze security rsyslog.service' generates false output in some cases, see below.

Version-Release number of selected component (if applicable):
systemd-239-75.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. systemd-analyze security rsyslog.service
...
✗ SystemCallFilter=~@clock Service does not filter system calls  0.2
✗ SystemCallFilter=~@debug Service does not filter system calls  0.2
✗ SystemCallFilter=~@module Service does not filter system calls 0.2
✗ SystemCallFilter=~@mount Service does not filter system calls  0.2
✗ SystemCallFilter=~@raw-io Service does not filter system calls 0.2
✗ SystemCallFilter=~@reboot Service does not filter system calls 0.2
✗ SystemCallFilter=~@swap Service does not filter system calls 0.2
✗ SystemCallFilter=~@privileged Service does not filter system calls 0.2
✗ SystemCallFilter=~@resources Service does not filter system calls 0.2
...
3. After review, I added the following line to the rsyslog service file (/usr/lib/systemd/system/rsyslog.service):
SystemCallFilter=~@clock @debug @module @raw-io @reboot @swap @cpu-emulation @obsolete
4. systemctl daemon-reload && systemctl restart rsyslog

Actual results:
systemd-analyze still reports that the systemcallfilters are not present.

Expected results:
systemd-analyze should not report that the systemcallfilters are not present.

Additional info:
On rhel-9.3 with systemd-252-13.el9_2.x86_64, the problem can not be reproduced.

Comment 5 RHEL Program Management 2023-09-21 12:29:04 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 6 RHEL Program Management 2023-09-21 12:34:16 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.