Bug 1036854

Summary: starting pads generates SElinux write alert on /var/log/pads
Product: [Fedora] Fedora Reporter: pgaltieri <pgaltieri>
Component: padsAssignee: Steve Grubb <sgrubb>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: sgrubb
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:30:01 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:

Description pgaltieri 2013-12-02 18:48:50 UTC
Description of problem:
Starting pads generates SElinux alert


Version-Release number of selected component (if applicable):
pads-1.2-11.fc19.x86_64

How reproducible:
Always

Steps to Reproduce:
1. systemctl start pads
2.
3.

Actual results:
SElinux alert
SELinux is preventing /usr/bin/pads from write access on the directory /var/log/pads


Expected results:
pads should be able to write to /var/log/pads

Additional info:
Source Context                system_u:system_r:pads_t:s0
Target Context                unconfined_u:object_r:var_log_t:s0
Target Objects                /var/log/pads [ dir ]
Source                        pads
Source Path                   /usr/bin/pads
Port                          <Unknown>
Host                          jackstraw.homenet192-10.com
Source RPM Packages           pads-1.2-11.fc19.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.12.1-74.13.fc19.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     jackstraw.homenet192-10.com
Platform                      Linux jackstraw.homenet192-10.com
                              3.11.9-200.fc19.x86_64 #1 SMP Wed Nov 20 21:22:24
                              UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-12-02 10:40:37 PST
Last Seen                     2013-12-02 10:40:37 PST
Local ID                      12732d15-d55f-4264-ad8b-a52c8dba16f2

Raw Audit Messages
type=AVC msg=audit(1386009637.763:22391): avc:  denied  { write } for  pid=4142 comm="pads" name="pads" dev="dm-1" ino=917926 scontext=system_u:system_r:pads_t:s0 tcontext=unconfined_u:object_r:var_log_t:s0 tclass=dir


type=SYSCALL msg=audit(1386009637.763:22391): arch=x86_64 syscall=open success=no exit=EACCES a0=f58fb0 a1=241 a2=1b6 a3=0 items=0 ppid=1 pid=4142 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=pads exe=/usr/bin/pads subj=system_u:system_r:pads_t:s0 key=(null)

Hash: pads,pads_t,var_log_t,dir,write

Comment 1 Fedora End Of Life 2015-01-09 20:45:34 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-02-17 19:30:01 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.