#23136: moat integration (fetch bridges for the user) ---------------------------------------+------------------------------ Reporter: mcs | Owner: brade Type: defect | Status: needs_review Priority: Very High | Milestone: Component: Applications/Tor Launcher | Version: Severity: Normal | Resolution: Keywords: TorBrowserTeam201802R | Actual Points: Parent ID: #24689 | Points: Reviewer: | Sponsor: Sponsor4 ---------------------------------------+------------------------------
Comment (by mcs): Replying to [comment:45 anonym]: > (Sorry if this is off topic.) > > In Tails there was recently some work on getting `obfs4proxy`'s `meek_lite` transport to work. I've quickly looked at Tor Launcher's Moat code and I can see that it will only find the Meek client's path for `ClientTransportPlugin` lines specifying exactly `meek` -- I wonder, if Tor launcher also would accept `meek_lite` for Moat, would that be enough for its needs? I don't know how much work it would be to add support for `meek_lite`, but in theory it should be fairly easy to do so. For Tor Browser we decided to use the full-blown meek client because (1) we already have it inside Tor Browser and (2) using it means the client's TLS fingerprint will match that of a well-known browser (since a second copy of Tor Browser/firefox is used via `meek-client-torbrowser`). That said, it is possible that there will be some interoperability issues between `meek_lite` and BridgeDB's Moat responder. But if you need this, please open a ticket against Tor Launcher. And of course "patches are welcome" :) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23136#comment:46> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs