[tbb-bugs] #12776 [Tor Browser]: Move meek's URL and front configuration into bridge_prefs.js

Tor Bug Tracker & Wiki blackhole at torproject.org
Mon Aug 4 16:10:35 UTC 2014

#12776: Move meek's URL and front configuration into bridge_prefs.js
     Reporter:  dcf          |      Owner:  tbb-team
         Type:  defect       |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Tor Browser  |    Version:
   Resolution:               |   Keywords:  meek TorBrowserTeam201408
Actual Points:               |  Parent ID:
       Points:               |

Comment (by dcf):

 Replying to [comment:1 gk]:
 > Replying to [ticket:12776 dcf]:
 > > On the other hand, if you're planning to do any meek bundles based on
 maint-3.6, you don't want this, because it won't work with tor 0.2.4.
 > You mean we don't want this for the maint-3.6 branch while it would
 still be perfectly fine to merge it to master and use it for all (alpha,
 beta...) releases containing a tor 0.2.5.x, right?

 Yes, that's right. I built a test release off of master with this patch
 and it worked fine.

 In fact building maint-3.6 with anything newer than
 transports/meek.git/shortlog/refs/tags/0.7 meek 0.7] (current is
 transports/meek.git/shortlog/refs/tags/0.10 0.10]) will fail, because of
 the paths that changed in #11641. I made a special
 transports/meek.git/shortlog/refs/heads/maint-3.6 maint-3.6] branch of
 meek with new code but old paths, in order to build the
 bundle.git/shortlog/refs/tags/tbb-3.6.3-meek-2 3.6.3-meek-2] bundle
 announced here], but I hope we won't have to use a special branch much

 (Incidentally, the reason meek has to know TBB paths is #12716, but I
 haven't found a nice solution to that yet.)

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

More information about the tbb-bugs mailing list