tor/changes/ticket40106

  o Minor bugfixes (config, bridge):
    - Don't initiate a connection to a bridge without a corresponding
      transport. Fixes bug 40106; bugfix on 0.4.5.1-alpha.
    - This also reverts an earlier fix we did for this that would validate
      configuration to avoid such situation but turns out it wouldn't work for
      a DisableNetwork thus the new approach.
config: Catch missing Bridge for ClientTransportPlugin When making sure we have a Bridge line with a ClientTransportPlugin, we now check in the managed proxy list and so we can catch any missing ClientTransportPlugin for a Bridge line. Fixes #40106 Signed-off-by: David Goulet <dgoulet@torproject.org> 2020-12-08 16:01:23 +01:00			`o Minor bugfixes (config, bridge):`
config: Remove Bridge <-> ClientTransportPlugin validation This validation was only done if DisableNetwork was off because we would use the global list of transports/bridges and DisableNetwork would not populate it. This was a problem for any user using DisableNetwork which includes Tor Browser and thus leading to the Bug() warning. Without a more in depth refactoring, we can't do this validation without the global list. The previous commit makes it that any connection to a bridge without a transport won't happen thus we keep the security feature of not connecting to a bridge without its corresponding transport. Related to #40106 Signed-off-by: David Goulet <dgoulet@torproject.org> 2021-01-20 17:24:47 +01:00			`- Don't initiate a connection to a bridge without a corresponding`
			`transport. Fixes bug 40106; bugfix on 0.4.5.1-alpha.`
			`- This also reverts an earlier fix we did for this that would validate`
			`configuration to avoid such situation but turns out it wouldn't work for`
			`a DisableNetwork thus the new approach.`