[tbb-dev] Request for help: debugging Moat in Tails

[David Fifield]

For some basic debugging, you should check that these commands work to
talk to the endpoint of the meek tunnel:

	$ curl https://onion.azureedge.net/
	I’m just a happy little web server.
	$ curl -H 'Host: onion.azureedge.net' https://ajax.aspnetcdn.com/
	I’m just a happy little web server.

If those work, you can try communicating with Moat through the tunnel.
You will need to run obfs4proxy and pass it specially formatted SOCKS
credentials that encode the url= and front= parameters. You will have to
change the XXXXX port number to match what obfs4proxy outputs in the
CMETHOD line.

	$ TOR_PT_MANAGED_TRANSPORT_VER=1 TOR_PT_STATE_LOCATION=pt_state TOR_PT_CLIENT_TRANSPORTS=meek_lite /usr/local/lib/obfs4proxy/obfs4proxy
	VERSION 1
	CMETHOD meek_lite socks5 127.0.0.1:XXXXX
	CMETHODS DONE

	$ curl --proxy socks5://url%3Dhttps%3A%2F%2Fonion.azureedge.net:%2F at 127.0.0.1:XXXXX/ https://bridges.torproject.org/moat/
	{"errors": [{"id": "0", "type": "", "version": "0.1.0", "code": 501, "status": "Not Implemented", "detail": "moat version 0.1.0 does not implement GET /moat/"}]}

	$ curl --proxy socks5://url%3Dhttps%3A%2F%2Fonion.azureedge.net%2F%3Bfront=ajax.aspnetcdn.co:m at 127.0.0.1:XXXXX/ https://bridges.torproject.org/moat/
	{"errors": [{"id": "0", "type": "", "version": "0.1.0", "code": 501, "status": "Not Implemented", "detail": "moat version 0.1.0 does not implement GET /moat/"}]}