[tor-bugs] #24636 [Obfuscation/BridgeDB]: moat-transports response not sent

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Dec 19 00:05:02 UTC 2017


#24636: moat-transports response not sent
----------------------------------+----------------------
 Reporter:  mcs                   |          Owner:  isis
     Type:  defect                |         Status:  new
 Priority:  Medium                |      Milestone:
Component:  Obfuscation/BridgeDB  |        Version:
 Severity:  Normal                |     Resolution:
 Keywords:                        |  Actual Points:
Parent ID:                        |         Points:
 Reviewer:                        |        Sponsor:
----------------------------------+----------------------

Comment (by isis):

 I totally specified this differently than the behaviour, sorry.

 Now I'm wondering if I should just change the spec to match the actual
 behaviour? Would that be okay with you? My reasoning is that, if there
 were no commonly-supported transports, sending the list of transports that
 BridgeDB ''does'' support back at the same time as a new CAPTCHA
 potentially saves a roundtrip (should the user/agent decide they can
 actually support one of the available transports).

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


More information about the tor-bugs mailing list