#24432: The meek<->moat tunneling isn't set up correctly ----------------------------------+-------------------------- Reporter: isis | Owner: isis Type: defect | Status: new Priority: High | Milestone: Component: Obfuscation/BridgeDB | Version: Severity: Normal | Resolution: Keywords: moat bridgedb-dist | Actual Points: Parent ID: | Points: 2 Reviewer: | Sponsor: SponsorM ----------------------------------+--------------------------
Comment (by dcf): It works for me with a few changes. {{{ $ ./externalize-pt-client.sh meek/meek-client/meek-client -url https ://tor-bridges-hyphae-channel.appspot.com/ -front www.google.com $ curl --proxy socks5://127.0.0.1:10000/ https://bridges.torproject.org/moat/fetch {"errors": [{"status": "Not Implemented", "code": 501, "detail": "moat version 0.1.0 does not implement GET /moat/fetch", "version": "0.1.0", "type": "", "id": 0}]} }}} 4-dot-tor-bridges-hyphae-channel.appspot.com indeed seems to be misconfigured (giving the redirect you described), but tor-bridges-hyphae- channel.appspot.com seems to work. Going to https://tor-bridges-hyphae-channel.appspot.com/moat/fetch in a browser is not going to work, because the `/moat/fetch` is at the wrong layer. The appspot.com domain is just a tunneling mechanism and doesn't use any URL paths. The moat communication, including URL paths, has to happen inside the tunnel. In other words, * meek-client (outside of tunnel) uses !https://tor-bridges-hyphae- channel.appspot.com/ * curl (inside of tunnel) uses !https://bridges.torproject.org/moat/fetch (which indeed it is tunneling to) -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24432#comment:3> 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