Fedora Account System
Red Hat Associate
Red Hat Customer
The default configuration shipped with IRC proxy `bip` listens on port 7778 and writes logs to /var/log/bip{/*,.conf}, but SELinux policy currently restricts this behavior. Something like this seems to do the job: """ module bip 1.0; require { type var_log_t; type bitlbee_t; type unreserved_port_t; class tcp_socket name_connect; class file open; } #============= bitlbee_t ============== #!!!! This avc can be allowed using the boolean 'nis_enabled' allow bitlbee_t unreserved_port_t:tcp_socket name_connect; allow bitlbee_t var_log_t:file open; """ Please provide a default policy for bip.
e4de19a464ba6c6ba6dcd22d99762ade04c3dd3e should fix the var_log issue. Currently bitlbee domains get this access for network. bitlbee_t: tcp name_connect 56, 80, 81, 443, 488, 8008, 8009, 8443, 9000 (http_port_t) 1721, 7000 (gatekeeper_port_t) 1863 (msnp_port_t) 5050 (mmcc_port_t) 88, 750, 4444 (kerberos_port_t) -- Allowed False [ nis_enabled=0 || kerberos_enabled=0 ] 389, 636, 3268, 7389 (ldap_port_t) -- Allowed True [ nis_enabled=0 || authlogin_nsswitch_use_ldap=1 ] 5190-5193 (aol_port_t) 5222, 5223 (jabber_client_port_t) 53 (dns_port_t) 6667, 6697 (ircd_port_t) 8080, 8118, 8123, 10001-10010 (http_cache_port_t) 8955 (dnssec_port_t) 9080 (ocsp_port_t) -- Allowed False [ kerberos_enabled=0 ] bitlbee_t: tcp name_bind 6667, 6697 (ircd_port_t) 7778 (interwise_port_t) Should we label port 7778 with one of these types or define a new one?
That's a better question for the `bip` maintainer, I think. Brian, care to weigh in?
bip should be listening to port 6667, we comment out the port = 7778 config entry in the sample config.
Pete, could you add raw AVC msg for allow bitlbee_t unreserved_port_t:tcp_socket name_connect; rule. I added additional fixes.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.