Regarding this quote:
When the same bridge is configured multiple times with the same identity, but at different address:port combinations, treat those bridge instances as separate guards. This fix restores the ability of clients to configure the same bridge with multiple pluggable transports. Fixes bug 21027

Yes, but are you able to make tor mark those "semi-separate" bridge instances as belonging to the same family, since they are the same guy? Otherwise, a malicious bridge may somehow end up in multiple circuits of the same user, more often than acceptable, and observe more traffic than it should?


  • Lines and paragraphs break automatically.
  • Allowed HTML tags: <em> <strong> <cite> <code> <ul> <ol> <li> <b> <i> <strike> <p> <br>

More information about formatting options

Syndicate content