tor/changes/bug21027

  o Major bugfixes (bridges):

    - When the same bridge is configured multiple times at different
      address:port combinations (but with the same identity), treat
      those bridge instances as separate guards. This allows clients to
      configure the same bridge with multiple pluggable transports, once
      again. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
Change approach to preventing duplicate guards. Previously I'd made a bad assumption in the implementation of prop271 in 0.3.0.1-alpha: I'd assumed that there couldn't be two guards with the same identity. That's true for non-bridges, but in the bridge case, we allow two bridges to have the same ID if they have different addr:port combinations -- in order to have the same bridge ID running multiple PTs. Fortunately, this assumption wasn't deeply ingrained: we stop enforcing the "one guard per ID" rule in the bridge case, and instead enforce "one guard per <id,addr,port>". We also needed to tweak our implementation of get_bridge_info_for_guard, since it made the same incorrect assumption. Fixes bug 21027; bugfix on 0.3.0.1-alpha. 2017-02-14 18:21:31 +01:00			`o Major bugfixes (bridges):`

			`- When the same bridge is configured multiple times at different`
			`address:port combinations (but with the same identity), treat`
			`those bridge instances as separate guards. This allows clients to`
			`configure the same bridge with multiple pluggable transports, once`
			`again. Fixes bug 21027; bugfix on 0.3.0.1-alpha.`