Policies for HTTPTunnelPort

For SocksPort/Socks5Port one can configure SocksPolicy. There should be corresponding option for HTTPTunnelPort.

Trac:
Username: pyhedgehog

changed milestone to %Tor: unspecified

added component::core tor/tor milestone::Tor: unspecified priority::medium reporter::pyhedgehog severity::normal status::new tor-httptunnel type::enhancement labels

Looking at the code, it appears that SocksPolicy is applied to all incoming client connections. (See uses of socks_policy_permits_address().) We should probably document this behavior and rename SocksPolicy to something less confusing. Maybe ClientPolicy?

I'd prefer to have several policies for different ports. I.e. I want to configure:

HTTPTunnelPort 0.0.0.0:3128 NoOnionTraffic
HTTPTunnelPort 0.0.0.0:8118 OnionTrafficOnly
SocksPort 127.0.0.1:9050

And want to have different policies for different ports.

Trac:
Username: pyhedgehog

Trac:
Milestone: N/A to Tor: unspecified

Trac:
Status: new to assigned
Owner: N/A to neel

Trac:
Status: assigned to new

Trac:
Status: new to assigned
Owner: neel to N/A

Make everything that is assigned to no-one new again.

Trac:
Status: assigned to new

Trac:
Keywords: N/A deleted, tor-httptunnel added

moved to tpo/core/tor#25786 (closed)