Snowflake

Snowflake is a new WebRTC pluggable transport inspired by Flashproxy.

It is currently in alpha, reliably bootstrapping a Tor client to 100% and providing a reasonable browsing experience with Tor Browser.

However, Snowflake is under active development. It is not yet considered stable or audited, and should not yet be relied upon for any critical use-cases.


To embed the Snowflake badge on any website:

This should look like:

If it animates, then congratulations – you are currently acting as a Tor bridge.


Interested to learn more about how it works? See the Technical Writeup (Draft)

Repo:

https://gitweb.torproject.org/pluggable-transports/snowflake.git/

FAQ

Q: How does it work?

In the Tor use-case:

Volunteers visit websites which host the “snowflake” proxy. (just like flashproxy) Tor clients automatically find available browser proxies via the Broker (the domain fronted signaling channel). Tor client and browser proxy establish a WebRTC peer connection. Proxy connects to some relay. Tor occurs.

More detailed information about how clients, snowflake proxies, and the Broker fit together is available here.

Q: What are the benefits of this PT compared with other PTs?

Snowflake combines the advantages of flashproxy and meek. Primarily:

It has the convenience of Meek, but can support magnitudes more users with negligible CDN costs. (Domain fronting is only used for brief signalling / NAT-piercing to setup the P2P WebRTC DataChannels which handle the actual traffic.)

Arbitrarily high numbers of volunteer proxies are possible like in flashproxy, but NATs are no longer a usability barrier - no need for manual port forwarding!

Q: Why is this called Snowflake?

It utilizes the “ICE” negotiation via WebRTC, and also involves a great abundance of ephemeral and short-lived (and special!) volunteer proxies…


Last update: 2016-08-01

~serene

Last Update: 2016-06-25 00:00 UTC