snowflake/client
Cecylia Bocovich bf924445e3 Implement NAT discovery (RFC 5780) at the client
Snowflake clients will now attempt NAT discovery using the provided STUN
servers and report their NAT type to the Snowflake broker for matching.
The three possibilities for NAT types are:
- unknown (the client was unable to determine their NAT type),
- restricted (the client has a restrictive NAT and can only be paired
with unrestricted NATs)
- unrestricted (the client can be paired with any other NAT).
2020-07-06 13:16:03 -04:00
..
lib Implement NAT discovery (RFC 5780) at the client 2020-07-06 13:16:03 -04:00
client_test.go Touched up snowflake client tests 2019-12-06 11:30:34 -05:00
README.md Remove copy/paste signalling 2019-05-08 11:21:56 -04:00
snowflake.go Implement NAT discovery (RFC 5780) at the client 2020-07-06 13:16:03 -04:00
torrc Change dummy address for snowflake 2020-04-01 12:55:37 -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.