| Summary: | SELinux is preventing /bin/bash from using the 'signal' accesses on a process. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pierre-YvesChibon <pingou> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 14 | CC: | dominick.grift, dwalsh, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:80b3c8d8d7244ebcee43abef473c8f742d64973e9b3169d77259779e472d30c7 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 16:49:28 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Is there a postfix process running as unconfined_t? Did you execute a postfix domain directly without using a service script? # ps -eZ |grep postfix There is a postfix process running and the error is generated while running the service postfix restart, see below: # service postfix restart Shutting down postfix: [FAILED] Starting postfix: [FAILED] # ps -eZ |grep postfix # How did postfix-script get started? When the machine started I assume unconfined_t is a user login process label, it should not happen at boot. If you run # restorecon -R -v /etc do you see any init scripts being relabeled? # restorecon -R -v /etc restorecon reset /etc/ssh/ssh_host_rsa_key context unconfined_u:object_r:etc_t:s0->system_u:object_r:sshd_key_t:s0 restorecon reset /etc/ssh/ssh_host_dsa_key context unconfined_u:object_r:etc_t:s0->system_u:object_r:sshd_key_t:s0 restorecon reset /etc/ssh/ssh_host_key context unconfined_u:object_r:etc_t:s0->system_u:object_r:sshd_key_t:s0 restorecon reset /etc/X11/xorg.conf.d/00-system-setup-keyboard.conf context system_u:object_r:etc_runtime_t:s0->system_u:object_r:etc_t:s0 restorecon reset /etc/postfix/postfix-script context unconfined_u:object_r:postfix_etc_t:s0->system_u:object_r:postfix_exec_t:s0 restorecon reset /etc/dovecot.conf context unconfined_u:object_r:etc_t:s0->system_u:object_r:dovecot_etc_t:s0 But I still have: # service postfix restart Shutting down postfix: [FAILED] Starting postfix: [FAILED] This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
SELinux is preventing /bin/bash from using the 'signal' accesses on a process. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that bash should be allowed signal access on processes labeled unconfined_t 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 postfix-script /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:system_r:postfix_master_t:s0 Target Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Objects Unknown [ process ] Source postfix-script Source Path /bin/bash Port <Unknown> Host (removed) Source RPM Packages bash-4.1.7-4.fc14 Target RPM Packages Policy RPM selinux-policy-3.9.7-44.fc14 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.35.14-97.fc14.x86_64 #1 SMP Sat Sep 17 00:15:37 UTC 2011 x86_64 x86_64 Alert Count 3 First Seen Sun 30 Oct 2011 10:33:17 AM CET Last Seen Sun 30 Oct 2011 10:34:14 AM CET Local ID fdc189f6-4883-4601-9def-f175c98f36a3 Raw Audit Messages type=AVC msg=audit(1319967254.671:84): avc: denied { signal } for pid=3666 comm="postfix-script" scontext=unconfined_u:system_r:postfix_master_t:s0 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=process type=SYSCALL msg=audit(1319967254.671:84): arch=x86_64 syscall=kill success=no exit=EACCES a0=d66 a1=f a2=0 a3=1999999999999999 items=0 ppid=3659 pid=3666 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=5 comm=postfix-script exe=/bin/bash subj=unconfined_u:system_r:postfix_master_t:s0 key=(null) Hash: postfix-script,postfix_master_t,unconfined_t,process,signal audit2allow #============= postfix_master_t ============== allow postfix_master_t unconfined_t:process signal; audit2allow -R #============= postfix_master_t ============== allow postfix_master_t unconfined_t:process signal;