#25875: Azure meek bridge bootstrap fails without meek-client-torbrowser proxy ------------------------------+------------------------------- Reporter: habib | Owner: dcf Type: defect | Status: new Priority: Medium | Milestone: Component: Obfuscation/meek | Version: Tor: 0.3.2.10 Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------+-------------------------------
Comment (by dcf): Could you attach your torrc file? It is indeed weird that, according to your log, || ||= amazon =||= azure =|| ||= meek-client=|| works || doesn't work || ||= meek-client-torbrowser=|| ^(not tested)^ || works || You can try adding `-log meek-client.log` to the `ClientTransportPlugin` line, to get some lower-level logs. Replying to [comment:1 cypherpunks]: > The meek client is more and more coupled to the Tor Browser. For a standalone app you may try to use `meek_lite` with obfs4proxy. Only meek-client-torbrowser is coupled to Tor Browser. meek-client by itself is independent. I think the bug reporter is doing it right. meek- client by itself is basically the same as meek_lite. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25875#comment:2> 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