Bug 755172
| Summary: | permit openvpn to access to tor socks port | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Michael S. <misc> |
| Component: | selinux-policy-targeted | Assignee: | Miroslav Grepl <mgrepl> |
| Status: | CLOSED ERRATA | QA Contact: | Ben Levenson <benl> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | dwalsh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-3.10.0-64.fc16 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-12-06 01:05:25 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: | |||
Mhh, it seems that I left several important point. What I attempted to do is to use openvpn over tor, with a server listening on port 443/tcp. The problem is due to some DPI gateway preventing me to using openvpn ( I do not have much more info on the network, that's wifi for some free software events in south of france, and the admin are not here ). So I fired tor in regular client mode ( ie, default configuration ), and said to network-manager to use a socks proxy for openvpn, on localhost 9050. Tor open a tcp connexion on port 9050, and speak socks5 protocol. So for more granularity, maybe the different type of port should be splitted, ie tor_socks_port_t, etc, so we can let openvpn connect to it, but not to the others ( openvpn or others, since polipo or polipo for example can also connect to tor with socks ). You believe that port 9050 should be labeled socks_port_t and then allow all apps that can currently use tor_port_t could then use socks_port_t, correct? Yep, sorry if I was not clear :/ Miroslav add 8c23816640766f435f36d27add6cb18885e18aa1 to RHEL6 and F16 policy. Added. selinux-policy-3.10.0-64.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-64.fc16 Package selinux-policy-3.10.0-64.fc16: * should fix your issue, * was pushed to the Fedora 16 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.10.0-64.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16698/selinux-policy-3.10.0-64.fc16 then log in and leave karma (feedback). selinux-policy-3.10.0-64.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |
openvpn network manager plugin permit to connect to a socks server ( or http ), and so does openvpn. yet, it seems selinux prevent connexion to port labelled tor_t as seen in this avc : [root@liliana selinux]# grep 1321695318.818:1969 /var/log/audit/audit.log type=AVC msg=audit(1321695318.818:1969): avc: denied { name_connect } for pid=9389 comm="openvpn" dest=9050 scontext=system_u:system_r:openvpn_t:s0 tcontext=system_u:object_r:tor_port_t:s0 tclass=tcp_socket type=SYSCALL msg=audit(1321695318.818:1969): arch=c000003e syscall=42 success=no exit=-13 a0=6 a1=7fff43f1fbb8 a2=10 a3=0 items=0 ppid=9376 pid=9389 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="openvpn" exe="/usr/sbin/openvpn" subj=system_u:system_r:openvpn_t:s0 key=(null)