Bug 1635385

Summary:	boltd is causing selinux alerts
Product:	[Fedora] Fedora	Reporter:	Samuel Sieb <samuel-rhbugs>
Component:	selinux-policy	Assignee:	Lukas Vrabec <lvrabec>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	28	CC:	bojan, ckellner, dwalsh, lvrabec, mgrepl, plautrba
Target Milestone:	---
Target Release:	---
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:	2018-10-04 13:13:10 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 Samuel Sieb 2018-10-02 19:20:05 UTC

boltd is causing three selinux alerts:

SELinux is preventing boltd from write access on the directory boltd.

SELinux is preventing boltd from add_name access on the directory power.

SELinux is preventing boltd from create access on the directory power.

Comment 1 Samuel Sieb 2018-10-02 19:24:27 UTC

Policy RPM                    selinux-policy-3.14.1-42.fc28.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing

Raw Audit Messages
type=AVC msg=audit(1538505198.882:146): avc:  denied  { write } for  pid=996 comm="boltd" name="boltd" dev="tmpfs" ino=32456 scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1

type=AVC msg=audit(1538505198.882:147): avc:  denied  { add_name } for  pid=996 comm="boltd" name="power" scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1

type=AVC msg=audit(1538505198.882:148): avc:  denied  { create } for  pid=996 comm="boltd" name="power" scontext=system_u:system_r:boltd_t:s0 tcontext=system_u:object_r:var_run_t:s0 tclass=dir permissive=1

Deleting the /var/run/boltd directory and starting the bolt service triggers the alerts.

Comment 2 Christian Kellner 2018-10-04 13:13:10 UTC


*** This bug has been marked as a duplicate of bug 1632230 ***