Bug 919830
| Summary: | SELinux is preventing /usr/bin/procmail from 'read' accesses on the file unix. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Juan Orti Alcaine <jorti> |
| Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 18 | CC: | dominick.grift, dwalsh, mgrepl |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | abrt_hash:ac8cceb003fa48348467d8b2da783d7aad65de5386b158f442024b2a890cfb57 | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-03-14 03:01:44 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: | |||
Fixed in selinux-policy-3.11.1-83.fc18. selinux-policy-3.11.1-85.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-85.fc18 Package selinux-policy-3.11.1-85.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-85.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-3605/selinux-policy-3.11.1-85.fc18 then log in and leave karma (feedback). selinux-policy-3.11.1-85.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: I don't know what happened, I just use Kmail with my gmail account SELinux is preventing /usr/bin/procmail from 'read' accesses on the file unix. ***** Plugin catchall (100. confidence) suggests *************************** If cree que de manera predeterminada, procmail debería permitir acceso read sobre unix file. Then debería reportar esto como un error. Puede generar un módulo de política local para permitir este acceso. Do permita el acceso momentáneamente executando: # grep procmail /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:procmail_t:s0 Target Context system_u:object_r:proc_net_t:s0 Target Objects unix [ file ] Source procmail Source Path /usr/bin/procmail Port <Unknown> Host (removed) Source RPM Packages procmail-3.22-31.fc18.x86_64 Target RPM Packages Policy RPM selinux-policy-3.11.1-82.fc18.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.8.1-201.fc18.x86_64 #1 SMP Thu Feb 28 19:23:08 UTC 2013 x86_64 x86_64 Alert Count 2 First Seen 2013-03-10 12:00:01 CET Last Seen 2013-03-10 12:15:02 CET Local ID fa2da5e3-6567-44da-b394-d5be22ca3662 Raw Audit Messages type=AVC msg=audit(1362914102.115:388): avc: denied { read } for pid=3169 comm="procmail" name="unix" dev="proc" ino=4026532002 scontext=system_u:system_r:procmail_t:s0 tcontext=system_u:object_r:proc_net_t:s0 tclass=file type=SYSCALL msg=audit(1362914102.115:388): arch=x86_64 syscall=access success=no exit=EACCES a0=7fff3f0dd4a0 a1=4 a2=7fff3f0dd4ae a3=1c items=0 ppid=3168 pid=3169 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 ses=4294967295 tty=(none) comm=procmail exe=/usr/bin/procmail subj=system_u:system_r:procmail_t:s0 key=(null) Hash: procmail,procmail_t,proc_net_t,file,read audit2allow #============= procmail_t ============== allow procmail_t proc_net_t:file read; audit2allow -R #============= procmail_t ============== allow procmail_t proc_net_t:file read; Additional info: hashmarkername: setroubleshoot kernel: 3.8.1-201.fc18.x86_64 type: libreport Potential duplicate: bug 868615