Snowflake issueshttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues2022-03-01T19:17:35Zhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40015Investigate high retransmission rate of Snowflake2022-03-01T19:17:35ZCecylia BocovichInvestigate high retransmission rate of SnowflakeThe recent report on Snowflake distinguishability caught the fact that Snowflake has a very high rate of retransmissions during the handshake: https://arxiv.org/pdf/2008.03254.pdf
This was reported to cause latency and it sounds like a ...The recent report on Snowflake distinguishability caught the fact that Snowflake has a very high rate of retransmissions during the handshake: https://arxiv.org/pdf/2008.03254.pdf
This was reported to cause latency and it sounds like a bug. It could also apply to the rest of the connection after the handshake. We should look into this.Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40014Make Snowflake's DTLS fingerprint more similar to popular WebRTC implementations2024-01-12T17:12:10ZCecylia BocovichMake Snowflake's DTLS fingerprint more similar to popular WebRTC implementationsSome recent work by researchers at Princeton shows that Snowflake's DTLS fingerprint differs from some other popular WebRTC implementations (Facebook, Google, and Discord): https://arxiv.org/pdf/2008.03254.pdf
I'm hesitant to rush chang...Some recent work by researchers at Princeton shows that Snowflake's DTLS fingerprint differs from some other popular WebRTC implementations (Facebook, Google, and Discord): https://arxiv.org/pdf/2008.03254.pdf
I'm hesitant to rush changes to the fingerprint without a more complete comparison to more WebRTC implementations popular in censored regions. But, we can get a start on figuring out how to change the fingerprint in pion and see whether we will need to submit upstream patches to provide us with this kind of agility. Something like uTLS would be great for us in the long run.Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibettheodorsmtheodorsmhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/31085Make an Android extension or app for people to be a snowflake (AMO or proxy-go)2023-07-13T14:59:01ZcypherpunksMake an Android extension or app for people to be a snowflake (AMO or proxy-go)https://addons.mozilla.org/en-US/android/https://addons.mozilla.org/en-US/android/Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/29863Add disk space monitoring for snowflake infrastructure2023-07-31T02:23:24ZCecylia BocovichAdd disk space monitoring for snowflake infrastructureWe've run out of disk space at both the snowflake bridge (legacy/trac#26661, legacy/trac#28390) and the broker (legacy/trac#29861), which has caused snowflake to stop working. We've set up rotating and compressed logs but it would be nic...We've run out of disk space at both the snowflake bridge (legacy/trac#26661, legacy/trac#28390) and the broker (legacy/trac#29861), which has caused snowflake to stop working. We've set up rotating and compressed logs but it would be nice to have some disk space monitoring to alert us if/when this happens again
Also, as discussed on IRC, we should eventually move the broker to a TPA machine.Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibethttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/25598Let the broker inform proxies how often to poll2022-07-25T17:59:44ZDavid Fifielddcf@torproject.orgLet the broker inform proxies how often to pollCurrently, proxies poll the broker at a static rate of once every 5–10 seconds. If we're anticipating thousands of proxies, we don't need them to poll so frequently.
The broker could instead tell each proxy how long to wait before polli...Currently, proxies poll the broker at a static rate of once every 5–10 seconds. If we're anticipating thousands of proxies, we don't need them to poll so frequently.
The broker could instead tell each proxy how long to wait before polling again. The broker could even dynamically adjust the rate based on an estimate of supply and demand.
One way to do this would be a custom header in responses to `/proxy` requests:
```
Snowflake-Next-Poll: Thu, 22 Mar 2018 18:05:47 GMT
```
Or using a relative time offset:
```
Snowflake-Next-Poll: 600
```
There was a similar idea for flash proxy.
legacy/trac#8171::
The facilitator included a fixed `check-back-in=600` in its responses.
legacy/trac#8172::
Adjust polling interval dynamically (never implemented).Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet