mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-27 07:59:35 +01:00
803e769fb2
Now that tor automatically binds to IPv4 _and_ IPv6, in order to avoid breaking configurations, we sanitize the parsed lists for duplicate ORPorts. It is possible to happen because we still allow this configuration; ORPort 9888 ORPort [4242::1]:9888 Meaning that the first ORPort value will bind to 0.0.0.0:9888 _and_ [::]:9888 which would lead to an error when attempting to bind on [4242::1]:9888. However, that configuration is accepted today and thus we must not break it. To remedy, we now sanitize the parsed list and prioritize an ORPort that has an explicit address over the global one. A warning is emitted if such configuration pattern is found. This is only for the ORPort. Related to #33246 Signed-off-by: David Goulet <dgoulet@torproject.org> |
||
|---|---|---|
| .. | ||
| api | ||
| client | ||
| control | ||
| dirauth | ||
| dircache | ||
| dirclient | ||
| dircommon | ||
| dirparse | ||
| hibernate | ||
| hs | ||
| hs_common | ||
| keymgt | ||
| nodelist | ||
| relay | ||
| rend | ||
| stats | ||
| feature.md | ||