Bug 1003236
Summary: | SELinux is preventing /usr/bin/polipo from 'name_connect' accesses on the tcp_socket . | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | vikram goyal <vikigoyal> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 18 | CC: | dominick.grift, dwalsh, lvrabec, mgrepl |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:e1a3b68a511ca213f34827b7cb1fb4c631dd0e8aa60bda4392d6a1feb547fdc2 | ||
Fixed In Version: | selinux-policy-3.11.1-103.fc18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-09-23 00:43:05 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
vikram goyal
2013-09-01 08:23:02 UTC
Hi Vikram, You could turn on Boolean, while we close this bug. setsebool -P polipo_connect_all_unreserved 1 Hello, I did that but there also was a suggestion to create a local policy, which I did & loaded it judiciously:) The local policy thus generated is as under. Posting it below for your reference. Also, I was wondering if, isn't it better that polipo should be restricted to DNS port only rather than all ports below 1023. Just an inquisitiveness, I'm not an expert though. Thanks. [root@vikram ~]# cat /etc/polipo/mypol.te module mypol 1.0; require { type net_conf_t; type chrome_sandbox_t; type tor_socks_port_t; type user_home_dir_t; type ladvd_t; type sysfs_t; type var_lock_t; type bin_t; type apcupsd_t; type sysctl_net_t; type polipo_t; type var_run_t; class process { signal setcap }; class capability { net_admin setpcap }; class tcp_socket name_connect; class file { read create open execute }; class sock_file create; class udp_socket connect; } #============= apcupsd_t ============== allow apcupsd_t var_lock_t:file read; #============= chrome_sandbox_t ============== allow chrome_sandbox_t user_home_dir_t:file create; #============= ladvd_t ============== allow ladvd_t bin_t:file execute; allow ladvd_t net_conf_t:file open; allow ladvd_t self:capability { net_admin setpcap }; allow ladvd_t self:process { signal setcap }; allow ladvd_t self:udp_socket connect; allow ladvd_t sysctl_net_t:file open; allow ladvd_t sysfs_t:file open; allow ladvd_t var_run_t:sock_file create; #============= polipo_t ============== #!!!! This avc is allowed in the current policy allow polipo_t tor_socks_port_t:tcp_socket name_connect; Thank you Vikram for your help but we have found solution how fix this bug. :) selinux-policy-3.11.1-103.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-103.fc18 Package selinux-policy-3.11.1-103.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-103.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-16344/selinux-policy-3.11.1-103.fc18 then log in and leave karma (feedback). selinux-policy-3.11.1-103.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |