#24432: The meek<->moat tunneling isn't set up correctly
 Reporter:  isis                  |          Owner:  isis
     Type:  defect                |         Status:  closed
 Priority:  High                  |      Milestone:
Component:  Obfuscation/BridgeDB  |        Version:
 Severity:  Normal                |     Resolution:  fixed
 Keywords:  moat bridgedb-dist    |  Actual Points:
Parent ID:  #24689                |         Points:  2
 Reviewer:                        |        Sponsor:  SponsorM
Changes (by isis):

 * status:  reopened => closed
 * resolution:   => fixed


 Replying to [comment:33 mcs]:
 > Replying to [comment:30 isis]:
 > > @mcs Do you want to test with your TB against the production server
 > I did, and it is working. Awesome!


 > We had to change our Tor Launcher Moat client code to send the `id`s as
 strings instead of integers, but that was a trivial change.

 I thought I would need to fix this in the spec too, but the spec already
 said they should be strings not ints, so I was actually doing it wrong

 > We also switched from asking for `vanilla` bridges to asking for `obfs4`
 ones, because that is what works (I assume the bridges you assigned to the
 Moat distributor were obfs4 ones). For some reason I thought we were
 supposed to request vanilla bridges, but I don't remember where I got that
 idea. Please let Kathy and I know if it is okay to assume that Tor
 Launcher will be able to receive obfs4 bridges via Moat for the
 foreseeable future.

 There are plenty of `obfs4` bridges, so if it's doable on your side
 perhaps we should go with that? They should work better in more countries
 and get blocked less often than vanilla ones, so it'll probably provide a
 better user experience to not have to fill out as many captchas.

 Tentatively closing as "fixed", but of course feel free to reopen if
 there's any more issues.

Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24432#comment:34>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
tor-bugs mailing list

Reply via email to