Bug 447454

After relabeling the system, setroubleshoot speaks to me again:

--- 8< ---
Summary:

SELinux is preventing tlsmgr (postfix_master_t) "write" to ./postfix
(var_lib_t).

Detailed Description:

SELinux is preventing tlsmgr (postfix_master_t) "write" to ./postfix
(var_lib_t). The SELinux type var_lib_t, is a generic type for all files in the
directory and very few processes (SELinux Domains) are allowed to write to this
SELinux type. This type of denial usual indicates a mislabeled file. By default
a file created in a directory has the gets the context of the parent directory,
but SELinux policy has rules about the creation of directories, that say if a
process running in one SELinux Domain (D1) creates a file in a directory with a
particular SELinux File Context (F1) the file gets a different File Context
(F2). The policy usually allows the SELinux Domain (D1) the ability to write,
unlink, and append on (F2). But if for some reason a file (./postfix) was
created with the wrong context, this domain will be denied. The usual solution
to this problem is to reset the file context on the target file, restorecon -v
'./postfix'. If the file context does not change from var_lib_t, then this is
probably a bug in policy. Please file a bug report
(http://bugzilla.redhat.com/bugzilla/enter_bug.cgi) against the selinux-policy
package. If it does change, you can try your application again to see if it
works. The file context could have been mislabeled by editing the file or moving
the file from a different directory, if the file keeps getting mislabeled, check
the init scripts to see if they are doing something to mislabel the file.

Allowing Access:

You can attempt to fix file context by executing restorecon -v './postfix'

Fix Command:

restorecon './postfix'

Additional Information:

Source Context                unconfined_u:system_r:postfix_master_t:s0
Target Context                system_u:object_r:var_lib_t:s0
Target Objects                ./postfix [ dir ]
Source                        tlsmgr
Source Path                   /usr/libexec/postfix/tlsmgr
Port                          <Unknown>
Host                          wombat
Source RPM Packages           postfix-2.5.1-2.fc9
Target RPM Packages           
Policy RPM                    selinux-policy-3.3.1-51.fc9
Selinux Enabled               True
Policy Type                   targeted
MLS Enabled                   True
Enforcing Mode                Enforcing
Plugin Name                   mislabeled_file
Host Name                     wombat
Platform                      Linux wombat 2.6.25.3-18.fc9.x86_64 #1 SMP Tue May
                              13 04:54:47 EDT 2008 x86_64 x86_64
Alert Count                   2
First Seen                    Tue 20 May 2008 01:44:53 AM CEST
Last Seen                     Tue 20 May 2008 01:46:55 AM CEST
Local ID                      0838bcc0-c587-4d8f-a130-920c98c45832
Line Numbers                  

Raw Audit Messages            

host=wombat type=AVC msg=audit(1211240815.811:43): avc:  denied  { write } for 
pid=4941 comm="tlsmgr" name="postfix" dev=dm-3 ino=720990
scontext=unconfined_u:system_r:postfix_master_t:s0
tcontext=system_u:object_r:var_lib_t:s0 tclass=dir

host=wombat type=SYSCALL msg=audit(1211240815.811:43): arch=c000003e syscall=2
success=no exit=-13 a0=7f535ff6e920 a1=42 a2=180 a3=7fff66e03db0 items=0
ppid=4734 pid=4941 auid=500 uid=0 gid=0 euid=89 suid=0 fsuid=89 egid=89 sgid=0
fsgid=89 tty=(none) ses=1 comm="tlsmgr" exe="/usr/libexec/postfix/tlsmgr"
subj=unconfined_u:system_r:postfix_master_t:s0 key=(null)
--- >8 ---

chcon -R -t postfix_var_lib_t /var/lib/postfix

should fix.

Fixed in selinux-policy-3.3.1-53.fc9.noarch

(In reply to comment #2)
> chcon -R -t postfix_var_lib_t /var/lib/postfix
> 
> should fix.

Tha seems to do it. Thanks for the quick response!

*** Bug 447450 has been marked as a duplicate of this bug. ***

I confirm that selinux-policy-3.3.1-53.fc9 fixes the problem for me (Bug 447450).

The fix seems not to be mentioned in the package changelog?

Closing all bugs that have been in modified for over a month.  Please reopen if the bug is not actually fixed.