snowflake/client
Cecylia Bocovich 1364d7d45b Move snowflake ConnectLoop inside SOCKS Handler
Bug #21314: maintains a separate snowflake connect loop per SOCKS
connection. This way, if Tor decides to stop using Snowflake, Snowflake
will stop using the client's network.
2020-08-27 16:43:55 -04:00
..
lib Move snowflake ConnectLoop inside SOCKS Handler 2020-08-27 16:43:55 -04:00
client_test.go Choose a random subset from given STUN servers 2020-07-23 11:30:36 -04:00
README.md Remove copy/paste signalling 2019-05-08 11:21:56 -04:00
snowflake.go Move snowflake ConnectLoop inside SOCKS Handler 2020-08-27 16:43:55 -04:00
torrc Choose a random subset from given STUN servers 2020-07-23 11:30:36 -04:00
torrc-localhost Change dummy address for snowflake 2020-04-01 12:55:37 -04:00

This is the Tor client component of Snowflake.

It is based on goptlib.

Flags

The client uses these following torrc options by default:

ClientTransportPlugin snowflake exec ./client \
-url https://snowflake-broker.azureedge.net/ \
-front ajax.aspnetcdn.com \
-ice stun:stun.l.google.com:19302

-url should be the URL of a Broker instance.

-front is an optional front domain for the Broker request.

-ice is a comma-separated list of ICE servers. These can be STUN or TURN servers.