Bug 2062936

Summary: SELinux prevents the aide process from doing connectto on the /run/systemd/userdb/io.systemd.Machine socket
Product: Red Hat Enterprise Linux 9 Reporter: Amith <apeetham>
Component: selinux-policyAssignee: Nikola Knazekova <nknazeko>
Status: CLOSED ERRATA QA Contact: Amith <apeetham>
Severity: medium Docs Contact:
Priority: low    
Version: 9.0CC: lvrabec, mmalik, nknazeko, rsroka
Target Milestone: rcKeywords: Triaged
Target Release: 9.2   
Hardware: s390x   
OS: Linux   
Whiteboard:
Fixed In Version: selinux-policy-34.1.44-1.el9 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-09 08:16:08 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:

Comment 1 Zdenek Pytela 2022-04-22 16:04:59 UTC
Radovan,

According to this BZ, aide tries to connect to systemd-machined. Can this request be considered correct and thus should be allowed in the policy? Furthermore, is it expected that it appears on one architecture only?

Comment 2 Radovan Sroka 2022-08-02 11:52:15 UTC
(In reply to Zdenek Pytela from comment #1)
> Radovan,
> 
> According to this BZ, aide tries to connect to systemd-machined. Can this
> request be considered correct and thus should be allowed in the policy?
> Furthermore, is it expected that it appears on one architecture only?

Hello Zdenek,

I believe it is OK to allow it.

Comment 3 Zdenek Pytela 2022-08-02 12:18:56 UTC
Thank you, Rado.

Comment 4 Nikola Knazekova 2022-10-11 14:50:26 UTC
PR: https://github.com/fedora-selinux/selinux-policy/pull/1435

Comment 14 errata-xmlrpc 2023-05-09 08:16:08 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (selinux-policy bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:2483