mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-30 23:53:32 +01:00
b5731cdf2e
It turns out that if _only_ the ControlPort is set and nothing else, tor would simply not bootstrap and thus not start properly. Commit67a41b6306removed that requirement for tor to be considered a "client". Unfortunately, this made the mainloop enable basically nothing if only the ControlPort is set in the torrc. This commit now makes it that we also consider the ControlPort when deciding if we are a Client or not. It does not revert67a41b6306meaning options_any_client_port_set() stays the same, not looking at the control port. Fixes #27849. Signed-off-by: David Goulet <dgoulet@torproject.org>
6 lines
312 B
Plaintext
6 lines
312 B
Plaintext
o Major bugfixes (mainloop, bootstrap):
|
|
- Make sure Tor bootstraps and works properly if only the ControlPort is
|
|
set. Prior to this fix, Tor would only bootstrap with at least a client
|
|
port being set (Socks, Trans, NATD, DNS or HTTPTunnel port). Fixes bug
|
|
27849; bugfix on 0.3.4.1-alpha.
|