torproject / tor / 10350

66%

cron

travis-ci

<a href="https://github.com/torproject/tor/commit/<a class=hub.com/torproject/tor/commit/d425dbf04a6bbac7eae832bf51c2bfe061e2c426">d425dbf04<a href="https://github.com/torproject/tor/commit/d425dbf04a6bbac7eae832bf51c2bfe061e2c426">&quot;&gt;port: Don&amp;#39;t ignore ports of a different family

Commit </a><a class="double-link" href="https://github.com/torproject/tor/commit/<a class="double-link" href="https://github.com/torproject/tor/commit/c3a0f757964de0e8a24911d72abff5df20bb323c">c3a0f7579</a>">c3a0f7579</a><a href="https://github.com/torproject/tor/commit/d425dbf04a6bbac7eae832bf51c2bfe061e2c426"> added this feature for ORPort
that we ignore any port that is not the family of our default address when
parsing the port. So if port_parse_config() was called with an IPv4 default
address, all IPv6 address would be ignored.

That makes sense for ORPort since we call twice port_parse_config() for
0.0.0.0 and [::] but for the rest of the ports, it is not good since a
perfectly valid configuration can be:

  SocksPort 9050
  SocksPort [::1]:9050

Any non-ORPort only binds by default to an IPv4 except the ORPort that binds
to both IPv4 and IPv6 by default.

The fix here is to always parse all ports within port_parse_config() and then,
specifically for ORPort, remove the duplicates or superseding ones. The
warning is only emitted when a port supersedes another.

A unit tests is added to make sure SocksPort of different family always exists
together.

Fixes #40183

Signed-off-by: David Goulet <dgoulet@torproject.org>

6 of 6 new or added lines in 2 files covered. (100.0%)

51932 of 80485 relevant lines covered (64.52%)

40536.09 hits per line