Bug 1004330
| Summary: | SELinux is preventing /usr/bin/perl from 'write' accesses on the directory /. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Griffiths <fedora.jrg01> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | dominick.grift, dwalsh, lvrabec, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:8f04d5f4c9ebb4a2ca50a699387a93385d92b19516c3e36961ebbb8a3304e5a8 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-04 12:58:18 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
I definitely think this is a problem on your end, in that we don't want your spam programs writing to /. It could be an app coredumping. I guess you have to figure out why it is happening. Some times apps try to open content in their homedir and if they are blocked as root will try to open in /. |
Description of problem: SELinux is preventing /usr/bin/perl from 'write' accesses on the directory /. Not sure why or what was trying to be written to /, so not sure if it should be allowed. Reporting to get feedback. ***** Plugin catchall_boolean (89.3 confidence) suggests ******************* If you want to allow all daemons to write corefiles to / Then you must tell SELinux about this by enabling the 'daemons_dump_core' boolean. You can read 'None' man page for more details. Do setsebool -P daemons_dump_core 1 ***** Plugin catchall (11.6 confidence) suggests *************************** If you believe that perl 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 2F7573722F62696E2F7370616D6420 /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:spamd_t:s0 Target Context system_u:object_r:root_t:s0 Target Objects / [ dir ] Source 2F7573722F62696E2F7370616D6420 Source Path /usr/bin/perl Port <Unknown> Host (removed) Source RPM Packages perl-5.16.3-265.fc19.x86_64 Target RPM Packages filesystem-3.2-13.fc19.x86_64 Policy RPM selinux-policy-3.12.1-73.fc19.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.10.10-200.fc19.x86_64 #1 SMP Thu Aug 29 19:05:45 UTC 2013 x86_64 x86_64 Alert Count 8 First Seen 2013-08-29 04:26:26 EDT Last Seen 2013-09-04 05:03:41 EDT Local ID 3368fe8f-52e9-4f39-9029-21e1d4e74c33 Raw Audit Messages type=AVC msg=audit(1378285421.841:3421): avc: denied { write } for pid=12634 comm=2F7573722F62696E2F7370616D6420 name="/" dev="dm-1" ino=2 scontext=system_u:system_r:spamd_t:s0 tcontext=system_u:object_r:root_t:s0 tclass=dir type=SYSCALL msg=audit(1378285421.841:3421): arch=x86_64 syscall=open success=no exit=EACCES a0=5903400 a1=441 a2=1b6 a3=0 items=0 ppid=12632 pid=12634 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=2F7573722F62696E2F7370616D6420 exe=/usr/bin/perl subj=system_u:system_r:spamd_t:s0 key=(null) Hash: 2F7573722F62696E2F7370616D6420,spamd_t,root_t,dir,write Additional info: reporter: libreport-2.1.6 hashmarkername: setroubleshoot kernel: 3.10.10-200.fc19.x86_64 type: libreport