[tor-bugs] #24432 [Obfuscation/BridgeDB]: The meek<->moat tunneling isn't set up correctly

[Tor Bug Tracker & Wiki]

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

Comment (by isis):

 Okay! Hooray. I've tagged a new version with all these fixes, and uploaded
 to this ticket
 [https://trac.torproject.org/projects/tor/attachment/ticket/24432/moat-
 fetch-and-format-captcha-response_v2.py a fixed version of the test
 script].

 Doing

 {{{
 TEST_PRODUCTION_MOAT=1 ./test-moat fetch > /tmp/moat-fetch
 ./moat-fetch-and-format-captcha-response_v2.py
 }}}

 And (successfully) completing the CAPTCHA, I get the following response:

 {{{
 {"data": [{"qrcode": null, "bridges": ["obfs4 REDACTED:REDACTED REDACTED
 cert=REDACTED iat-mode=0", "obfs4 REDACTED:REDACTED REDACTED cert=REDACTED
 iat-mode=0"], "version": "0.1.0", "type": "moat-bridges", "id": "3"}]}
 }}}

 If I instead type gibberish for the CAPTCHA solution, I get:

 {{{
 {"errors": [{"status": "No You're A Teapot", "code": 419, "detail": "The
 CAPTCHA solution was incorrect.", "version": "0.1.0", "type": "moat-
 bridges", "id": "4"}]}
 }}}

 And if I request a new CAPTCHA and solve it, I get the same two bridges as
 were first returned.

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