snowflake/client
Cecylia Bocovich 114df695ce Create new smux session for each SOCKS connection
Each SOCKS connection has its own set of snowflakes and broker poll
loop. Since the session manager was tied to a single set of snowflakes,
this resulted in a bug where RedialPacketConn would sometimes try to
pull snowflakes from a previously melted pool. The fix is to maintain
separate smux sessions for each SOCKS connection, tied to its own
snowflake pool.
2020-12-04 11:17:13 -05:00
..
lib Create new smux session for each SOCKS connection 2020-12-04 11:17:13 -05: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 Set max number of snowflakes in the Tongue 2020-08-27 16:44:07 -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.