Bug 728957
Summary: | User managed fetchmail forbidden after selinux upgrade | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Paolo Loggia <sentenza> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED ERRATA | QA Contact: | Milos Malik <mmalik> |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 5.7 | CC: | dwalsh, mmalik |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | selinux-policy-2.4.6-318.el5 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-02-21 05:47:49 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: |
Description
Paolo Loggia
2011-08-08 13:35:05 UTC
If you were in enforcing mode this process would not be allowed to get to this file. What is in .fetchmailrc? Even if the file is in the home directory of the user? most of the time just this few lines: set daemon 5 set logfile /home/user01/fetchmail.log poll mail.mydomain.in user user01 most user connect to an internal imap server, some to an external server. And i have to say that it worked fine before. I will treat it like in the procmail policy HOME_DIR/\.procmailrc -- gen_context(system_u:object_r:procmail_home_t, s0) /root/\.procmailrc -- gen_context(system_u:object_r:procmail_home_t, s0) list_dirs_pattern(procmail_t, procmail_home_t, procmail_home_t) read_files_pattern(procmail_t, procmail_home_t, procmail_home_t) userdom_search_user_home_dirs(procmail_t) userdom_search_admin_dir(procmail_t) Fixed in selinux-policy-2.4.6-318.el5 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0158.html |