[tor-relays] Snowflake PT

[teor]

Hi,

> On 23 Aug 2018, at 10:16, Mirimir <mirimir at riseup.net> wrote:
> 
> On 08/22/2018 04:17 PM, teor wrote:
>> Hi,
>> 
>> I don’t know about the current deployment plan for Snowflake, but I
>> can point you to the relevant parts of the git repository:
>> 
>>> On 22 Aug 2018, at 07:58, Nathaniel Suchy <me at lunorian.is> wrote:
>>> 
>>> Tor Browser 8 Alpha includes the Snowflake PT as it comes near a final release, the adoption and usage of the Snowflake PT will continue to rise. I now have the following questions...
>>> 
>>> 1) Will a command line tool like an obfs4proxy come out so those of us with infrastructure can run high capacity snowflake bridges.
>> 
>> Like Meek, Snowflake is a 3-component transport:
>> 
>> User -> Proxy -> Bridge
> 
> I've read some of the Snowflake documentation. But I've found it
> confusing.

The FAQ explains the different components:
https://github.com/keroserene/snowflake#faq

> I vaguely recall that Snowflake came up in a recent Tor
> browser install.

Yes, the *Snowflake client* is in the new Tor Browser alpha.

> And I vaguely recall that there was an option to act as
> a Snowflake proxy, via WebRTC. Is that true?

Yes, volunteers on non-censored connections can run the *Snowflake proxy*.

(Running a proxy in Tor Browser is not possible, because Tor Browser
disables WebRTC.)

> And if so, what IP address
> would be exposed? Would it be the IP address of the device running Tor
> browser? That would be rather iffy. Almost like inviting users to run
> relays, no? But perhaps I'm just confused.

The Snowflake client connects to the Snowflake proxy.

Snowflake uses the STUN WebRTC method, so clients and proxies discover
each others’ external IP addresses.

If Snowflake used the TURN method, then the TURN server would discover
both addresses:
https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/client/rendezvous.go#n141

T

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20180823/3f314d34/attachment.sig>