[tbb-bugs] #18517 [Tor Browser]: meek is broken in Tor Browser 6.0a3

Tor Bug Tracker & Wiki blackhole at torproject.org
Sun Mar 20 00:15:45 UTC 2016

#18517: meek is broken in Tor Browser 6.0a3
 Reporter:  gk           |          Owner:  tbb-team
     Type:  defect       |         Status:  new
 Priority:  Very High    |      Milestone:
Component:  Tor Browser  |        Version:
 Severity:  Normal       |     Resolution:
 Keywords:  regression   |  Actual Points:
Parent ID:               |         Points:
 Reviewer:               |        Sponsor:  None

Comment (by dcf):

 Replying to [comment:4 teor]:
 > I think this is a Tor Browser issue and we should adopt dcf's workaround
 of changing the dummy IP addresses to publicly routable IP addresses.

 Could we get some guidance on what false IP addresses to use? It's a flaw
 in the PT spec that bridge specifications have to have an IP address, even
 if the transport doesn't use it. I tried to make the IP addresses as fake-
 looking as possible, to try and make it obvious that they are unused.

 I don't think it's a good idea the IP address of whatever relay the PT
 eventually carries the traffic to, because it's not reflective of what's
 going on. If the bridge changes its IP address, the bridge line will keep
 working with the "wrong" address, and that's likely to be confusing.

 Could we use something in e.g. the reserved range? Or the
 [https://tools.ietf.org/html/rfc5737 range reserved for
 examples]? Maybe a bogus IPv6 address?

 But by all means, let's apply any workaround in Tor Browser, because now
 6.0a4 is out and presumably also has this problem.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18517#comment:5>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

More information about the tbb-bugs mailing list