Bug 916738 - SELinux preventing procmail_t to read proc_net_t files
Summary: SELinux preventing procmail_t to read proc_net_t files
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2013-02-28 19:58 UTC by steinach2810
Modified: 2013-03-14 03:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-03-14 03:04:05 UTC
Type: Bug

Attachments (Terms of Use)
selinux troubleshooter details (2.37 KB, text/plain)
2013-02-28 19:59 UTC, steinach2810
no flags Details

Description steinach2810 2013-02-28 19:58:02 UTC
from time to time i get an selinux warning from selinux troubleshooter in fedora 18 x86_64. the selinux troubleshooter gives the details in the attachment.

Comment 1 steinach2810 2013-02-28 19:59:08 UTC
Created attachment 703944 [details]
selinux troubleshooter details

Comment 2 Daniel Walsh 2013-02-28 21:07:51 UTC
bb28c39f2d49661fdb86da7887ee1d62b5c12d53 fixes this in Rawhide.

Comment 3 Fedora Update System 2013-03-04 12:11:52 UTC
selinux-policy-3.11.1-83.fc18 has been submitted as an update for Fedora 18.

Comment 4 Fedora Update System 2013-03-04 22:34:36 UTC
Package selinux-policy-3.11.1-83.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-83.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 5 Fedora Update System 2013-03-08 16:12:51 UTC
selinux-policy-3.11.1-84.fc18 has been submitted as an update for Fedora 18.

Comment 6 Fedora Update System 2013-03-14 03:04:07 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.