Bug 889946 - SELinux is preventing /usr/libexec/postfix/master from read, write access on the file master.pid.
Summary: SELinux is preventing /usr/libexec/postfix/master from read, write access on ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 17
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:dc7d9d2200c37416d8215a9592f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-24 06:09 UTC by Bill Thielman
Modified: 2012-12-27 10:51 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-12-27 10:51:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2012-12-24 06:09 UTC, Bill Thielman
no flags Details
File: hashmarkername (14 bytes, text/plain)
2012-12-24 06:09 UTC, Bill Thielman
no flags Details

Description Bill Thielman 2012-12-24 06:09:47 UTC
Additional info:
libreport version: 2.0.18
kernel:         3.6.10-2.fc17.i686

description:
:SELinux is preventing /usr/libexec/postfix/master from read, write access on the file master.pid.
:
:*****  Plugin catchall (100. confidence) suggests  ***************************
:
:If you believe that master should be allowed read write access on the master.pid 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:
:# grep master /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:
:Additional Information:
:Source Context                system_u:system_r:postfix_master_t:s0
:Target Context                unconfined_u:object_r:var_run_t:s0
:Target Objects                master.pid [ file ]
:Source                        master
:Source Path                   /usr/libexec/postfix/master
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           postfix-2.9.4-3.fc17.i686
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-161.fc17.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.6.10-2.fc17.i686 #1 SMP Tue Dec
:                              11 18:33:15 UTC 2012 i686 i686
:Alert Count                   1
:First Seen                    2012-12-23 22:34:05 EST
:Last Seen                     2012-12-23 22:34:05 EST
:Local ID                      55cac500-3a1a-4f18-9951-0a5802ef9c58
:
:Raw Audit Messages
:type=AVC msg=audit(1356320045.98:484): avc:  denied  { read write } for  pid=18741 comm="master" name="master.pid" dev="dm-2" ino=1188259 scontext=system_u:system_r:postfix_master_t:s0 tcontext=unconfined_u:object_r:var_run_t:s0 tclass=file
:
:
:type=SYSCALL msg=audit(1356320045.98:484): arch=i386 syscall=open success=no exit=EACCES a0=b8172a38 a1=8002 a2=0 a3=b8172a38 items=0 ppid=18735 pid=18741 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm=master exe=/usr/libexec/postfix/master subj=system_u:system_r:postfix_master_t:s0 key=(null)
:
:Hash: master,postfix_master_t,var_run_t,file,read,write
:
:audit2allow
:
:#============= postfix_master_t ==============
:allow postfix_master_t var_run_t:file { read write };
:
:audit2allow -R
:
:#============= postfix_master_t ==============
:allow postfix_master_t var_run_t:file { read write };
:

Comment 1 Bill Thielman 2012-12-24 06:09:50 UTC
Created attachment 668316 [details]
File: type

Comment 2 Bill Thielman 2012-12-24 06:09:52 UTC
Created attachment 668317 [details]
File: hashmarkername

Comment 3 Miroslav Grepl 2012-12-27 10:51:48 UTC
The problem is the master.pid file is mislabeled.

Did you run the service directly without using service script?

If you execute

# restorecon -R -v /var/run/dovecot

does it work then?


Note You need to log in before you can comment on or make changes to this bug.