| Summary: | SELinux is preventing /usr/bin/mailx from 'write' accesses on the directory /. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | akozumpl, dominick.grift, dwalsh, Jxanti.jx, lvrabec, mgrepl, mikhail.v.gavrilov, sivlemx |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:dcdddbabee0c4920068aab4b82ec168c5a1ed81fa3b0fe31080bc2fe457ee1b7 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-01-13 14:04:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
Any chance you know what you were doing when this happened? Dumping core? I am use debug kernel. May be. You could run in permissive mode and see what other AVC's you get. Description of problem: I changed from gnome3 to mate. After setting up everyhing I got this SELinux warning. I dont know what te reason is. Additional info: reporter: libreport-2.1.10 hashmarkername: setroubleshoot kernel: 3.11.10-301.fc20.i686+PAE type: libreport I am no seen this alert long time ago. So I think this https://bugzilla.redhat.com/show_bug.cgi?id=1043258 must trigger this alert. But no alert... *** This bug has been marked as a duplicate of bug 1043258 *** |
Description of problem: SELinux is preventing /usr/bin/mailx from 'write' accesses on the directory /. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that mailx should be allowed write access on the directory 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 mail /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:system_mail_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects / [ dir ] Source mail Source Path /usr/bin/mailx Port <Unknown> Host (removed) Source RPM Packages mailx-12.5-10.fc20.x86_64 Target RPM Packages filesystem-3.2-19.fc20.x86_64 Policy RPM selinux-policy-3.12.1-90.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.11.6-301.fc20.x86_64+debug #1 SMP Mon Oct 21 21:45:52 UTC 2013 x86_64 x86_64 Alert Count 2 First Seen 2013-10-27 21:42:40 YEKT Last Seen 2013-10-27 21:42:40 YEKT Local ID 19c54d58-bc95-4695-8c67-b46b10a2f74c Raw Audit Messages type=AVC msg=audit(1382888560.929:565): avc: denied { write } for pid=28526 comm="mail" name="/" dev="sdb1" ino=2 scontext=system_u:system_r:system_mail_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir type=SYSCALL msg=audit(1382888560.929:565): arch=x86_64 syscall=open success=no exit=EACCES a0=8b97a0 a1=441 a2=1b6 a3=c items=0 ppid=28525 pid=28526 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=mail exe=/usr/bin/mailx subj=system_u:system_r:system_mail_t:s0 key=(null) Hash: mail,system_mail_t,root_t,dir,write Additional info: reporter: libreport-2.1.8 hashmarkername: setroubleshoot kernel: 3.11.6-301.fc20.x86_64+debug type: libreport Potential duplicate: bug 682577