Bug 1401827

Summary: SELinux is preventing svnserve from 'getattr' accesses on the chr_file /dev/random.
Product: [Fedora] Fedora Reporter: hovercraft <hovercraft>
Component: selinux-policyAssignee: Lukas Vrabec <lvrabec>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: dominick.grift, dwalsh, lvrabec, mgrepl, plautrba, pmoore, ssekidde
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:749b16f056132150d8e9095bed0ebb8937056ab18ea42367b6512e3855425d35;VARIANT_ID=workstation;
Fixed In Version: selinux-policy-3.13.1-225.3.fc25 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-12 23:58:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description hovercraft 2016-12-06 08:20:35 UTC
Description of problem:
Subversion svnserve seems works, but periodically trigger selinux alert on attempt to access to /dev/random. I suspect it is its normal behaviour.
SELinux is preventing svnserve from 'getattr' accesses on the chr_file /dev/random.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that svnserve should be allowed getattr access on the random chr_file by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# ausearch -c 'svnserve' --raw | audit2allow -M my-svnserve
# semodule -X 300 -i my-svnserve.pp

Additional Information:
Source Context                system_u:system_r:svnserve_t:s0
Target Context                system_u:object_r:random_device_t:s0
Target Objects                /dev/random [ chr_file ]
Source                        svnserve
Source Path                   svnserve
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-224.fc25.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.8.6-300.fc25.x86_64 #1 SMP Tue
                              Nov 1 12:36:38 UTC 2016 x86_64 x86_64
Alert Count                   2
First Seen                    2016-12-06 14:57:15 +08
Last Seen                     2016-12-06 15:41:49 +08
Local ID                      cbab03d6-1103-49e4-bc82-e809e592279e

Raw Audit Messages
type=AVC msg=audit(1481010109.898:380): avc:  denied  { getattr } for  pid=11005 comm="svnserve" path="/dev/random" dev="devtmpfs" ino=1053 scontext=system_u:system_r:svnserve_t:s0 tcontext=system_u:object_r:random_device_t:s0 tclass=chr_file permissive=0


Hash: svnserve,svnserve_t,random_device_t,chr_file,getattr

Version-Release number of selected component:
selinux-policy-3.13.1-224.fc25.noarch

Additional info:
reporter:       libreport-2.8.0
hashmarkername: setroubleshoot
kernel:         4.8.6-300.fc25.x86_64
type:           libreport

Comment 1 Fedora Update System 2016-12-09 13:47:27 UTC
selinux-policy-3.13.1-225.3.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2016-f24b3ddc6a

Comment 2 Fedora Update System 2016-12-10 03:58:20 UTC
selinux-policy-3.13.1-225.3.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-f24b3ddc6a

Comment 3 Fedora Update System 2016-12-12 23:58:47 UTC
selinux-policy-3.13.1-225.3.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.