service tor start Hash String generated from selinux-policy-3.6.32-49.fc12,catchall,tor,tor_t,hplip_port_t,tcp_socket,name_bind audit2allow suggests:
Is tor supposed to bind to the hplip port? What port did it try to bind to? hplip_port_t tcp 1782, 2207, 2208, 8290, 50000, 50002, 8292, 9100, 9101, 9102, 9220, 9221, 9222, 9280, 9281, 9282, 9290, 9291, 9292
port can be configured freely; sample config uses port 9050 (socks5), 9051 (control) and 9001 (orport). Binding orport to 443 is very common too.
sorry, but this report is my mistake. Tor was configured to use alternative port jetdirect (9100/tcp). It is not necessary. This BugReport have to be closed.
Enrico tor can currently bind to tcp, 6969, s0, tcp,9001,s0, tcp,9030,s0, tcp,9050,s0, tcp,9051,s0 But not 443. Should I add a boolean to allow tor to connect to apache ports?
I suggest a boolean (defaulting to 'off') which allows binding to arbitrary ports. This eases setup of relay servers (see https://www.torproject.org/docs/tor-doc-relay) which are disabled by the sample configuration. Using non standard ports resp. ports like HTTPS makes it difficult to block access to the TOR network. Most users will need the socks5 and perhaps control ports only which default to 9050 + 9051.
Fixed in selinux-policy-3.6.32-56.fc12.noarch Add tor_bind_all_unreserved_ports boolean which allows it to bind to any port > 1024