#29627: Moat: add support for obfsproxy's meek_lite ---------------------------------------+------------------------------ Reporter: mcs | Owner: brade Type: defect | Status: needs_review Priority: Medium | Milestone: Component: Applications/Tor Launcher | Version: Severity: Normal | Resolution: Keywords: TorBrowserTeam201903R | Actual Points: Parent ID: #29430 | Points: Reviewer: | Sponsor: ---------------------------------------+------------------------------
Comment (by mcs): Replying to [comment:3 gk]: > We have `meekTransport`, `meekClientPath`, and `meekClientArgs` as parameters in `network-settings.js`. I wonder what happened to the `meek` part in `meekTransport` in `tl-bridgedb.jsm` as we only have `aTransport`/`mTransport` there. Maybe we don't need `meekTransport` but just `transport` in `network-seetings.js`? > > It's not that a big deal, I got just confused while reading over the code. Kathy and I think this is worth fixing. Here is a revised patch: https://gitweb.torproject.org/user/brade/tor- launcher.git/commit/?h=bug29627-02&id=99035eb7b6069c60fe4f97291abbea5af4fee886 -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/29627#comment:4> 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