Anti-censorship issueshttps://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues2023-03-07T15:49:08Zhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40254Nil Pointer Crash when Initializing Snowflake Proxy2023-03-07T15:49:08ZbimNil Pointer Crash when Initializing Snowflake Proxyhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/blob/main/proxy/lib/snowflake.go#L568
Line 568 ought to be moved below 589 - if the event dispatcher isn't set the proxy will crash. I came across this b...https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/blob/main/proxy/lib/snowflake.go#L568
Line 568 ought to be moved below 589 - if the event dispatcher isn't set the proxy will crash. I came across this bumping snowflake to the the latest release in Orbot via our IPtProxy wrapper library.
https://github.com/tladesignz/IPtProxy/issues/39
For now, we simply just init'd our own event dispatcher instance to sidestep the crash.https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/120Telegram GetBridgesBot is giving the same bridge to different users and repea...2023-06-21T09:16:58ZGusTelegram GetBridgesBot is giving the same bridge to different users and repeating the same bridge twiceTor Telegram bot GetBridgesBot is replying with the same bridge line and it's repeating twice (xxxx:8599).
Testing with another user, it shared 4 bridges, but gave xxxx:8599 bridge twice again.Tor Telegram bot GetBridgesBot is replying with the same bridge line and it's repeating twice (xxxx:8599).
Testing with another user, it shared 4 bridges, but gave xxxx:8599 bridge twice again.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/22Hang during startup2023-08-17T20:56:13ZVortHang during startupWhen I start conjure + Tor, nothing is happening for several minutes.
Looks like conjure encounter `i/o timeout`, but for some reason do not propagate this error to Tor.
Timeout by itself is not much of a problem, incorrect processin...When I start conjure + Tor, nothing is happening for several minutes.
Looks like conjure encounter `i/o timeout`, but for some reason do not propagate this error to Tor.
Timeout by itself is not much of a problem, incorrect processing of timeout is.
Here is what I see in Tor logs:
```text
Jan 27 11:38:53.000 [notice] Bootstrapped 0% (starting): Starting
Jan 27 11:38:53.000 [notice] Starting with guard context "bridges"
Jan 27 11:38:53.000 [notice] Delaying directory fetches: No running bridges
Jan 27 11:38:54.000 [notice] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
Jan 27 11:38:54.000 [notice] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
Jan 27 11:38:54.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
Jan 27 11:43:54.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 1; recommendation warn; host 0000000000000000000000000000000000000000 at 143.110.214.222:80)
Jan 27 11:43:54.000 [warn] 1 connections have failed:
Jan 27 11:43:54.000 [warn] 1 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
Jan 27 11:50:39.000 [warn] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 2; recommendation warn; host 0000000000000000000000000000000000000000 at 143.110.214.222:80)
Jan 27 11:50:39.000 [warn] 2 connections have failed:
Jan 27 11:50:39.000 [warn] 2 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
Jan 27 11:51:11.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
Jan 27 11:51:11.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
Jan 27 11:51:11.000 [notice] Application request when we haven't used client functionality lately. Optimistically trying known bridges again.
```
Here is what I see in conjure logs:
```text
[11:38:53] Redirecting log to file
2023/01/27 08:38:53 Started SOCKS listener at 127.0.0.1:49518
2023/01/27 08:38:54 SOCKS accepted: {143.110.214.222:80 url=https://registration.refraction.network.global.prod.fastly.net/api;front=cdn.sstatic.net map[front:[cdn.sstatic.net] url:[https://registration.refraction.network.global.prod.fastly.net/api]]}
2023/01/27 08:38:54 Attempting to connect to bridge at 143.110.214.222:80
2023/01/27 08:38:54 Using the registration API at https://registration.refraction.network.global.prod.fastly.net/api
[11:38:54] [0-993fa7] Shared Secret - 993fa79ab18355764b72929c0ab200426a6820e4e3b3296d9c20c7a67668d459
[11:38:54] [0-993fa7] covert 143.110.214.222:80
[11:38:54] [0-993fa7] Representative - a78b0aca057f22e950441300511844dfd611b9d30ee42ee9e3fb96c230eae5d5
[11:38:54] [0-993fa7] registering via APIRegistrarBidirectional
2023/01/27 08:38:54 Buffering 517 bytes to send later
2023/01/27 08:38:54 Performing a Conjure registration with domain fronting...
2023/01/27 08:38:54 Conjure station URL: https://registration.refraction.network.global.prod.fastly.net/api
2023/01/27 08:38:54 Domain front: cdn.sstatic.net
[11:38:55] [0-993fa7] bidirectional API registration succeeded
[11:38:55] [0-993fa7] sleeping for 1s
[11:38:56] [0-993fa7] Attempting to Connect ...
[11:38:56] [0-993fa7] Connected to phantom 2001:48a8:687f:1::a32 using transport 1
2023/01/27 08:38:56 Successfully connected to phantom proxy!
2023/01/27 08:38:56 Connected to bridge at 143.110.214.222:80
2023/01/27 08:38:56 Flushed 517 bytes from buffer
[11:38:57] [0-993fa7] failed to dial phantom 35.6.92.87: dial tcp 35.6.92.87:443: i/o timeout
2023/01/27 08:45:39 SOCKS accepted: {143.110.214.222:80 url=https://registration.refraction.network.global.prod.fastly.net/api;front=cdn.sstatic.net map[front:[cdn.sstatic.net] url:[https://registration.refraction.network.global.prod.fastly.net/api]]}
2023/01/27 08:45:39 Attempting to connect to bridge at 143.110.214.222:80
2023/01/27 08:45:39 Using the registration API at https://registration.refraction.network.global.prod.fastly.net/api
2023/01/27 08:45:39 Buffering 517 bytes to send later
[11:45:39] [1-d395fc] Shared Secret - d395fc83724535c06a8696810887780d39dc92c55906a672a8009d4f2959e25c
[11:45:39] [1-d395fc] covert 143.110.214.222:80
[11:45:39] [1-d395fc] Representative - 3fc023e0ac6e4a8561591b150a5744bd62d379ac9291899e248e1e60bbf10775
[11:45:39] [1-d395fc] registering via APIRegistrarBidirectional
2023/01/27 08:45:39 Performing a Conjure registration with domain fronting...
2023/01/27 08:45:39 Conjure station URL: https://registration.refraction.network.global.prod.fastly.net/api
2023/01/27 08:45:39 Domain front: cdn.sstatic.net
[11:45:40] [1-d395fc] bidirectional API registration succeeded
[11:45:40] [1-d395fc] sleeping for 1s
[11:45:41] [1-d395fc] Attempting to Connect ...
[11:45:41] [1-d395fc] Connected to phantom 35.8.49.148 using transport 1
2023/01/27 08:45:41 Successfully connected to phantom proxy!
2023/01/27 08:45:41 Connected to bridge at 143.110.214.222:80
2023/01/27 08:45:41 Flushed 517 bytes from buffer
[11:45:42] [1-d395fc] failed to dial phantom 2001:48a8:7fff:2:a1ae:301b:83bf:dd9d: dial tcp [2001:48a8:7fff:2:a1ae:301b:83bf:dd9d]:443: i/o timeout
2023/01/27 08:51:20 SOCKS accepted: {143.110.214.222:80 url=https://registration.refraction.network.global.prod.fastly.net/api;front=cdn.sstatic.net map[front:[cdn.sstatic.net] url:[https://registration.refraction.network.global.prod.fastly.net/api]]}
2023/01/27 08:51:20 Attempting to connect to bridge at 143.110.214.222:80
2023/01/27 08:51:20 Using the registration API at https://registration.refraction.network.global.prod.fastly.net/api
2023/01/27 08:51:20 Buffering 517 bytes to send later
[11:51:20] [2-e1613b] Shared Secret - e1613b624c8f3e54d59282f8d4b9e443f21bb99fbb00abdc35536be48fa0515d
[11:51:20] [2-e1613b] covert 143.110.214.222:80
[11:51:20] [2-e1613b] Representative - 22d161cbd51034061570b0e680a5170a4816666ef76cdcd6e12ca134fce80689
[11:51:20] [2-e1613b] registering via APIRegistrarBidirectional
2023/01/27 08:51:20 Performing a Conjure registration with domain fronting...
2023/01/27 08:51:20 Conjure station URL: https://registration.refraction.network.global.prod.fastly.net/api
2023/01/27 08:51:20 Domain front: cdn.sstatic.net
[11:51:20] [2-e1613b] bidirectional API registration succeeded
[11:51:20] [2-e1613b] sleeping for 1s
[11:51:21] [2-e1613b] Attempting to Connect ...
[11:51:22] [2-e1613b] Connected to phantom 141.219.104.210 using transport 1
2023/01/27 08:51:22 Successfully connected to phantom proxy!
2023/01/27 08:51:22 Connected to bridge at 143.110.214.222:80
2023/01/27 08:51:22 Flushed 517 bytes from buffer
[11:51:23] [2-e1613b] failed to dial phantom 2001:48a8:7fff:2:431b:5a3b:e14e:2515: dial tcp [2001:48a8:7fff:2:431b:5a3b:e14e:2515]:443: i/o timeout
```
Version: 49f2601b4af6b6e7cecd15d662ea7ee8cee5a7e4Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/76Toggle "Keep running when the browser is closed" doesn't activate when clicked2023-01-10T19:11:35ZcypherpunksToggle "Keep running when the browser is closed" doesn't activate when clickedInfos about my system :
Opera browser Version : 93.0.4585.37 (Stable)
System: Windows 10 64-bit
Chromium version: 107.0.5304.122
Version of the Snowflake chrome extension : 0.7.0
The toggle on the Snowflake web extension called "Keep ru...Infos about my system :
Opera browser Version : 93.0.4585.37 (Stable)
System: Windows 10 64-bit
Chromium version: 107.0.5304.122
Version of the Snowflake chrome extension : 0.7.0
The toggle on the Snowflake web extension called "Keep running when the browser is closed" doesn't activate . I've installed the extension through the Chrome web-store (since Opera can install extensions directly from the chrome webstore). But when I click on the toggle to activate it, nothing happens, it doesn't move, it doesn't activate and stays in the default disabled state. the other toggle titled "Enabled" above it works correctly though.https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/112Reported as offline in metrics, some bridges are online and running2024-02-29T15:22:53ZGusReported as offline in metrics, some bridges are online and runningSince last week, some bridge operators are reporting that their bridge is 'offline' in Metrics, but they are online and running.
I can confirm that this is happening. One of my bridges is marked as [offline](https://metrics.torproject....Since last week, some bridge operators are reporting that their bridge is 'offline' in Metrics, but they are online and running.
I can confirm that this is happening. One of my bridges is marked as [offline](https://metrics.torproject.org/rs.html#details/25A5B3BB5449EC5A0D4AE4DB657899C02C186EBE), but on the tor logs I see:
>Nov 28 12:02:57.000 [notice] Heartbeat: Since last heartbeat message, I have seen 200 unique clients.
Other messages on the logs:
```
Nov 20 12:23:29.000 [notice] Guard bauruine ($5B83DC983406651A0B4F6AE1940793CDD6A6F92E) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 198/283. Use counts are 63/63. 227 circuits completed, 0 were unusable, 30 collapsed, and 5 timed out. For reference, your timeout cutoff is 324 seconds.
Nov 20 23:04:10.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We're missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 5983/6034). That's ok. We will try to fetch missing descriptors soon.
Nov 21 03:24:31.000 [notice] Guard rixtyminutes ($01AE2DE314276C82FCCC3603A1C2F3238E6544C9) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 109/156. Use counts are 37/37. 132 circuits completed, 0 were unusable, 23 collapsed, and 5 timed out. For reference, your timeout cutoff is 324 seconds.
```
Reddit: https://www.reddit.com/r/TOR/comments/z2o7ro/bridge_metrics_showing_offline/meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/80is moat distributing bridges marked as blocked in russia?2024-03-07T18:10:20Zmeskiomeskio@torproject.orgis moat distributing bridges marked as blocked in russia?Someone has reported that moat/bridgedb is distributing bridges marked as blocked in russia (e.g. https://metrics.torproject.org/rs.html#details/1807BF9A521468998385F179DDBF928D2482A62C).Someone has reported that moat/bridgedb is distributing bridges marked as blocked in russia (e.g. https://metrics.torproject.org/rs.html#details/1807BF9A521468998385F179DDBF928D2482A62C).Sponsor 96: Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibetmeskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/33bridges.torproject.org retuns odd time for "Last tested: "2023-01-24T18:54:37Ztoralfbridges.torproject.org retuns odd time for "Last tested: "Yesterday I queried https://bridges.torproject.org/status?id=662D4E4DE2C883625C543DFA3C4EE466899E6C85 for the status of a new relay with nickname "hoppel" and got:
```
Last tested: 2022-04-01 01:22:29.996384489 +0000 UTC (17h20m3.267273...Yesterday I queried https://bridges.torproject.org/status?id=662D4E4DE2C883625C543DFA3C4EE466899E6C85 for the status of a new relay with nickname "hoppel" and got:
```
Last tested: 2022-04-01 01:22:29.996384489 +0000 UTC (17h20m3.267273954s ago)
```
The "time ago" looks odd b/c the public bridge was setup about just 2-3 hours ago (using ansible, accidently I run the setup few times in a row at different VPS ip addresses and forgot to not publish the bridge distributor for those tests).https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/72Some bridges don't have a valid status page2024-03-06T16:41:13ZCecylia BocovichSome bridges don't have a valid status page@gk found a bridge that doesn't have a valid status page, but it does show up in the extra info files that rdsys is using.
Relay search page: https://metrics.torproject.org/rs.html#details/47D7B70C2E411A941348AF2132D41BC4554FDD25
bridg...@gk found a bridge that doesn't have a valid status page, but it does show up in the extra info files that rdsys is using.
Relay search page: https://metrics.torproject.org/rs.html#details/47D7B70C2E411A941348AF2132D41BC4554FDD25
bridgestrap status page: https://bridges.torproject.org/status?id=47D7B70C2E411A941348AF2132D41BC4554FDD25
I've verified the bridge is in the extrainfo file. So rdsys seems to be throwing it out for some reason? If the bridge doesn't work, it should show up as dysfunctional but still be saved as a valid resource.meskiomeskio@torproject.orgmeskiomeskio@torproject.org2024-07-31https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40071Increase of "unknown" NAT assignments by probetest since 2021-10-252023-06-20T18:24:54ZDavid Fifielddcf@torproject.orgIncrease of "unknown" NAT assignments by probetest since 2021-10-25https://lists.torproject.org/pipermail/anti-censorship-team/2021-October/000197.html
> ...looking into the broker graphs there is something weird since 2 days. The number of proxies with 'unknown' type of nat has rised heavily at the sam...https://lists.torproject.org/pipermail/anti-censorship-team/2021-October/000197.html
> ...looking into the broker graphs there is something weird since 2 days. The number of proxies with 'unknown' type of nat has rised heavily at the same time the 'restricted' nat has gone down. There are long periods without idle proxies and many requests being denied of nat type uknown. It doesn't look like the proxy capacity has gone down, can it be something broken on the way we test the nat type?
It seems that something is going wrong with probetest. A past problem we had with probetest not functioning properly was #40039. Currently the probetest process is again using 100% CPU.
It is possible this is some kind of slow resource exhaustion, or it's possible that probetest is simply overloaded with the number of proxies we have currently. At the [2021-10-28 anti-censorship team meeting](http://meetbot.debian.net/tor-meeting/2021/tor-meeting.2021-10-28-16.00.log.html#l-51) we decided to restart probetest and watch it to see how quickly it returns to its failure state, in order to distinguish these two possibilities.shelikhooshelikhoohttps://gitlab.torproject.org/tpo/anti-censorship/bridgestrap/-/issues/27Bridgestrap prometheus metrics showing weird periodic behaviour2024-02-27T19:01:54ZCecylia BocovichBridgestrap prometheus metrics showing weird periodic behaviourFrom the grafana plots:
![Screenshot_from_2021-10-21_10-43-16](/uploads/ffcb2caa394de91999751f1cc9514af7/Screenshot_from_2021-10-21_10-43-16.png)
![Screenshot_from_2021-10-21_10-42-59](/uploads/0a6c5963a514d0663707f0bd1642f921/Screensh...From the grafana plots:
![Screenshot_from_2021-10-21_10-43-16](/uploads/ffcb2caa394de91999751f1cc9514af7/Screenshot_from_2021-10-21_10-43-16.png)
![Screenshot_from_2021-10-21_10-42-59](/uploads/0a6c5963a514d0663707f0bd1642f921/Screenshot_from_2021-10-21_10-42-59.png)
It's not failing to connect to all bridges during the period where the fraction of functional bridges is lower, but rather the highs and lows of the fraction of bridges seems to be caused by these large spikes of successes and failures.meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40064How to manage CPU saturation?2022-04-05T15:23:39ZJacobo NájeraHow to manage CPU saturation?Hi,
For several months I have been running various snowflake proxies with the standalone version. On two occasions I identified CPU saturation. I currently have a snowflake proxy that consumes between 90% and 100% CPU.
CPU usage
![Ca...Hi,
For several months I have been running various snowflake proxies with the standalone version. On two occasions I identified CPU saturation. I currently have a snowflake proxy that consumes between 90% and 100% CPU.
CPU usage
![Captura_de_pantalla_de_2021-08-29_22-08-45](/uploads/b6af9f8067d28e058559538e3d583c7e/Captura_de_pantalla_de_2021-08-29_22-08-45.png)
Connections
![Captura_de_pantalla_de_2021-08-30_23-28-50](/uploads/285a0f49645210e8beedb55b7e4d439d/Captura_de_pantalla_de_2021-08-30_23-28-50.png)
Software setup
- Docker image thetorproject/snowflake-proxy:latest
- Debian Buster
How to manage CPU saturation?
Thanks, Jacobohttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40057A weird issue about domain name resolution2022-03-01T15:55:27Zdebug996A weird issue about domain name resolutionDevelopers of Snowflake,
I have trouble to use the snowflake bridge to connect to Tor. To find out the main issue, I managed to collect the log of snowflake. (attached below)
It can be seen that the snowflake program tries to resolve h...Developers of Snowflake,
I have trouble to use the snowflake bridge to connect to Tor. To find out the main issue, I managed to collect the log of snowflake. (attached below)
It can be seen that the snowflake program tries to resolve host names from [::1]:53, but there is no dns server listening, nor is there a statement for [::1]:53 in /etc/resolv.conf .
```
--- Starting Snowflake Client ---
2021/07/24 07:12:11 Using ICE servers:
2021/07/24 07:12:11 url: stun:stun.sonetel.com:3478
2021/07/24 07:12:11 url: stun:stun.stunprotocol.org:3478
2021/07/24 07:12:11 url: stun:stun.dus.net:3478
2021/07/24 07:12:11 url: stun:stun.uls.co.za:3478
2021/07/24 07:12:11 url: stun:stun.voip.blackberry.com:3478
2021/07/24 07:12:11 url: stun:stun.sonetel.net:3478
2021/07/24 07:12:11 url: stun:stun.bluesip.net:3478
2021/07/24 07:12:11 Rendezvous using Broker at: https://snowflake-broker.torproject.net.global.prod.fastly.net/
2021/07/24 07:12:11 Domain fronting using: cdn.sstatic.net
2021/07/24 07:12:11 Started SOCKS listener at 127.0.0.1:39363.
2021/07/24 07:12:11 Error resolving address: lookup stun.sonetel.com on [::1]:53: read udp [::1]:60448->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.sonetel.com on [::1]:53: read udp [::1]:60448->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.stunprotocol.org on [::1]:53: read udp [::1]:46030->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.stunprotocol.org on [::1]:53: read udp [::1]:46030->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.dus.net on [::1]:53: read udp [::1]:46841->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.dus.net on [::1]:53: read udp [::1]:46841->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.uls.co.za on [::1]:53: read udp [::1]:51689->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.uls.co.za on [::1]:53: read udp [::1]:51689->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.voip.blackberry.com on [::1]:53: read udp [::1]:51608->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.voip.blackberry.com on [::1]:53: read udp [::1]:51608->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.sonetel.net on [::1]:53: read udp [::1]:35863->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.sonetel.net on [::1]:53: read udp [::1]:35863->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error resolving address: lookup stun.bluesip.net on [::1]:53: read udp [::1]:42763->[::1]:53: read: connection refused
2021/07/24 07:12:11 Error creating STUN connection: lookup stun.bluesip.net on [::1]:53: read udp [::1]:42763->[::1]:53: read: connection refused
2021/07/24 07:12:11 NAT Type: unknown
2021/07/24 07:12:11 SOCKS accepted: {192.0.2.3:1 map[]}
2021/07/24 07:12:11 ---- SnowflakeConn: begin collecting snowflakes ---
2021/07/24 07:12:11 ---- SnowflakeConn: starting a new session ---
2021/07/24 07:12:11 ---- SnowflakeConn: begin stream 3 ---
2021/07/24 07:12:11 redialing on same connection
2021/07/24 07:12:11 WebRTC: Collecting a new Snowflake. Currently at [0/1]
2021/07/24 07:12:11 snowflake-c33c6e11b0e8bdf9 connecting...
2021/07/24 07:12:11 WebRTC: DataChannel created.
2021/07/24 07:12:11 WebRTC: Created offer
2021/07/24 07:12:11 WebRTC: Set local description
2021/07/24 07:12:11 WebRTC: PeerConnection created.
2021/07/24 07:12:11 Negotiating via BrokerChannel...
Target URL: snowflake-broker.torproject.net.global.prod.fastly.net
Front URL: cdn.sstatic.net
2021/07/24 07:12:11 WebRTC: closing DataChannel
2021/07/24 07:12:11 WebRTC: closing PeerConnection
2021/07/24 07:12:11 WebRTC: Closing
2021/07/24 07:12:11 WebRTC: dial tcp: lookup cdn.sstatic.net on [::1]:53: read udp [::1]:41939->[::1]:53: read: connection refused Retrying...
2021/07/24 07:12:21 WebRTC: Collecting a new Snowflake. Currently at [0/1]
2021/07/24 07:12:21 snowflake-07b5e298791ef573 connecting...
2021/07/24 07:12:21 WebRTC: DataChannel created.
2021/07/24 07:12:21 WebRTC: Created offer
2021/07/24 07:12:21 WebRTC: Set local description
2021/07/24 07:12:21 WebRTC: PeerConnection created.
2021/07/24 07:12:21 Negotiating via BrokerChannel...
Target URL: snowflake-broker.torproject.net.global.prod.fastly.net
Front URL: cdn.sstatic.net
2021/07/24 07:12:21 WebRTC: closing DataChannel
2021/07/24 07:12:21 WebRTC: closing PeerConnection
2021/07/24 07:12:21 WebRTC: Closing
2021/07/24 07:12:21 WebRTC: dial tcp: lookup cdn.sstatic.net on [::1]:53: read udp [::1]:40102->[::1]:53: read: connection refused Retrying...
```https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40021Some CollecTor bridge pool assignment files are empty2022-03-01T17:36:51ZCecylia BocovichSome CollecTor bridge pool assignment files are emptyI was helping a friend debug some weird bridge churn results for a research project, and noticed that some of CollecTor's bridge pool assignment data files are empty. See for example the file for the timestamp `2021-06-11-19-30-05` retri...I was helping a friend debug some weird bridge churn results for a research project, and noticed that some of CollecTor's bridge pool assignment data files are empty. See for example the file for the timestamp `2021-06-11-19-30-05` retrievable from https://collector.torproject.org/archive/bridge-pool-assignments/bridge-pool-assignments-2021-06.tar.xz.
I'm not sure if this is a bug on the BridgeDB side or the CollecTor side, but it appears to happen regularly (about once a month, near the middle of the month). So we should do an initial investigation on our end and then contact the metrics team if we think this is a CollecTor bug.https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/40015eomReceived sometimes called on message with NoneType2022-05-19T09:21:39ZCecylia BocovicheomReceived sometimes called on message with NoneTypeI noticed this output when deploying BridgeDB. From what I can tell emails still work, I don't think this is a high priority bug right now, but it is definitely a bug.
```
Unhandled Error
Traceback (most recent call last):
File "/home...I noticed this output when deploying BridgeDB. From what I can tell emails still work, I don't think this is a high priority bug right now, but it is definitely a bug.
```
Unhandled Error
Traceback (most recent call last):
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/python/log.py", line 101, in callWithLogger
return callWithContext({"system": lp}, func, *args, **kw)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/python/log.py", line 85, in callWithContext
return context.call({ILogContext: newCtx}, func, *args, **kw)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/python/context.py", line 118, in callWithContext
return self.currentContext().callWithContext(ctx, func, *args, **kw)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/python/context.py", line 83, in callWithContext
return func(*args, **kw)
--- <exception caught here> ---
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/internet/posixbase.py", line 687, in _doReadOrWrite
why = selectable.doRead()
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/internet/tcp.py", line 246, in doRead
return self._dataReceived(data)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/internet/tcp.py", line 251, in _dataReceived
rval = self.protocol.dataReceived(data)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/protocols/basic.py", line 439, in dataReceived
self.lineReceived(line)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/mail/smtp.py", line 501, in lineReceived
return getattr(self, "state_" + self.mode)(line)
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/mail/smtp.py", line 748, in dataLineReceived
[m.eomReceived() for m in self.__messages], consumeErrors=True
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/twisted/mail/smtp.py", line 748, in <listcomp>
[m.eomReceived() for m in self.__messages], consumeErrors=True
File "/home/bridgedb/virtualenvs/bridgedb/lib/python3.7/site-packages/bridgedb-0.12.2+0.gee08b6b1.dirty-py3.7.egg/bridgedb/distributors/email/server.py", line 235, in eomReceived
if self.message.is_multipart():
builtins.AttributeError: 'NoneType' object has no attribute 'is_multipart'
```https://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-webext/-/issues/3Remove local LAN address ICE candidates from JS proxy answer2023-01-20T08:33:58ZArlo BreaultRemove local LAN address ICE candidates from JS proxy answerThis is a follow up from legacy/trac#19026 where it was done for the clients and golang proxies.This is a follow up from legacy/trac#19026 where it was done for the clients and golang proxies.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/33560Settings immediately after install2021-06-17T14:23:19ZTracSettings immediately after install3/9/20, 04:33:18.780 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
3/9/20, 04:33:19.122 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
3/9/20, 04:33:19.336 [NOTICE] Bootstrapped 15% (handshake_done): Handsh...3/9/20, 04:33:18.780 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
3/9/20, 04:33:19.122 [NOTICE] Bootstrapped 14% (handshake): Handshaking with a relay
3/9/20, 04:33:19.336 [NOTICE] Bootstrapped 15% (handshake_done): Handshake with a relay done
3/9/20, 04:33:19.337 [NOTICE] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
3/9/20, 04:33:19.338 [NOTICE] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
3/9/20, 04:33:19.340 [NOTICE] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
3/9/20, 04:33:20.168 [NOTICE] Bootstrapped 100% (done): Done
3/9/20, 04:33:21.105 [NOTICE] New control connection opened from 127.0.0.1.
3/9/20, 04:33:21.354 [NOTICE] New control connection opened from 127.0.0.1.
3/9/20, 04:34:59.416 [WARN] CreateProcessA() failed: The system cannot find the file specified.
3/9/20, 04:34:59.416 [WARN] Pluggable Transport process terminated with status code 0
3/9/20, 04:34:59.417 [WARN] Failed to start process: (null)
3/9/20, 04:34:59.417 [WARN] Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
3/9/20, 04:34:59.417 [NOTICE] Switching to guard context "bridges" (was using "default")
3/9/20, 04:34:59.504 [NOTICE] Delaying directory fetches: No running bridges
3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:34:59.504 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:00.507 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:00.508 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:00.509 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:01.511 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:02.523 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:03.529 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:03.529 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:04.542 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:04.543 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:05.546 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:06.556 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:06.556 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:07.582 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:07.583 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:07.584 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:08.567 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:09.575 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:09.576 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:11.593 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:12.611 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:14.621 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:15.635 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:16.645 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:17.648 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:18.660 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:19.672 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:22.546 [WARN] CreateProcessA() failed: The system cannot find the file specified.
3/9/20, 04:35:22.547 [WARN] Pluggable Transport process terminated with status code 0
3/9/20, 04:35:22.547 [WARN] Failed to start process: (null)
3/9/20, 04:35:22.548 [WARN] Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
3/9/20, 04:35:22.760 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:22.760 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:22.760 [NOTICE] Bridge at '96.41.145.139:42260' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:23.767 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:23.767 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:23.767 [NOTICE] Bridge at '96.41.145.139:42260' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:24.759 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:24.759 [NOTICE] Bridge at '96.41.145.139:42260' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:25.759 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:25.759 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:26.771 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:26.771 [NOTICE] Bridge at '96.41.145.139:42260' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:27.790 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:27.791 [NOTICE] Bridge at '5.2.75.181:9785' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:28.775 [NOTICE] Bridge at '217.12.199.130:42367' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:28.775 [NOTICE] Bridge at '96.41.145.139:42260' isn't reachable by our firewall policy. Asking bridge authority instead.
3/9/20, 04:35:29.290 [WARN] CreateProcessA() failed: The system cannot find the file specified.
3/9/20, 04:35:29.290 [WARN] Pluggable Transport process terminated with status code 0
3/9/20, 04:35:29.290 [WARN] Failed to start process: (null)
3/9/20, 04:35:29.300 [WARN] Managed proxy at 'TorBrowser\Tor\PluggableTransports\obfs4proxy.exe' failed at launch.
3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:29.761 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge '217.12.199.130:42367' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge '5.2.75.181:9785' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
3/9/20, 04:35:30.763 [WARN] We were supposed to connect to bridge '96.41.145.139:42260' using pluggable transport 'obfs4', but we can't find a pluggable transport proxy supporting 'obfs4'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
**Trac**:
**Username**: KatBloodgoodhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/10Probe Snowflake bridge from proxy 1x a day2022-04-05T17:04:55ZCecylia BocovichProbe Snowflake bridge from proxy 1x a dayWe're getting reports that the Snowflake bridge isn't reachable in legacy/trac#33364, but it's taking awhile for volunteers to notice because the probe check only happens once at installation or if you disable/enable the proxy.
Perhaps ...We're getting reports that the Snowflake bridge isn't reachable in legacy/trac#33364, but it's taking awhile for volunteers to notice because the probe check only happens once at installation or if you disable/enable the proxy.
Perhaps we can do the probe check 1x a day (e.g., when we do the stats refresh)?Arlo BreaultArlo Breaulthttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/lyrebird/-/issues/32439tor can't bootstrap with obfs4 bridge and skewed clock2022-06-22T07:35:54Zintrigeritor can't bootstrap with obfs4 bridge and skewed clockEnvironment: Debian unstable, Tor Browser 9.0.1, system clock set 2h in the future.
Observed behavior: Tor Launcher says "Connected to bridge" but the progress bar is stuck at a very low percentage. After a while, the "Copy Tor Log To C...Environment: Debian unstable, Tor Browser 9.0.1, system clock set 2h in the future.
Observed behavior: Tor Launcher says "Connected to bridge" but the progress bar is stuck at a very low percentage. After a while, the "Copy Tor Log To Clipboard" button appears.
Impact: Tails users whose hardware clock is set to local time, in a timezone that's not close enough to UTC, cannot use obfs4 bridges. Unfortunately, that's quite common, because:
* Windows sets the hardware clock to local time by default (as opposed to Unix systems, that tend to assume the hardware clock is in UTC)
* many places where one needs obfs4 to use Tor are 4-7 hours ahead of UTC
* Tails can't guess whether the hardware clock is set to UTC time or to local time; it assumes it's UTC time
Corresponding tor log (actual obfs4 bridges IP & port redacted):
```
11/9/19, 16:39:11.903 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/9/19, 16:39:11.903 [NOTICE] Switching to guard context "bridges" (was using "default")
11/9/19, 16:39:11.903 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/9/19, 16:39:11.903 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
11/9/19, 16:39:11.903 [NOTICE] Opening Socks listener on 127.0.0.1:9150
11/9/19, 16:39:11.903 [NOTICE] Opened Socks listener on 127.0.0.1:9150
11/9/19, 16:39:11.903 [NOTICE] Renaming old configuration file to "/home/toto/tor-browser_en-US/Browser/TorBrowser/Data/Tor/torrc.orig.1"
11/9/19, 16:39:12.885 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
11/9/19, 16:39:12.887 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
11/9/19, 16:40:06.330 [WARN] Proxy Client: unable to connect to $IP1:$PORT1 ("general SOCKS server failure")
11/9/19, 16:40:12.957 [WARN] Proxy Client: unable to connect to $IP2:$PORT2 ("general SOCKS server failure")
11/9/19, 16:40:13.120 [WARN] Proxy Client: unable to connect to $IP3:$PORT3 ("general SOCKS server failure")
11/9/19, 16:41:10.165 [WARN] Proxy Client: unable to connect to $IP1:$PORT1 ("general SOCKS server failure")
11/9/19, 16:41:14.240 [WARN] Proxy Client: unable to connect to $IP2:$PORT2 ("general SOCKS server failure")
11/9/19, 16:41:20.420 [WARN] Proxy Client: unable to connect to $IP3:$PORT3 ("general SOCKS server failure")
```https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/31847Expand contribution guidelines for snowflake2022-03-01T15:55:52ZCecylia BocovichExpand contribution guidelines for snowflakeWe're getting more contributors to the project, we should expand CONTRIBUTING.md with some more basic guidelines like
- formatting of commit messages
- creating tickets for each pull request
- make sure the changes in the commit adhere t...We're getting more contributors to the project, we should expand CONTRIBUTING.md with some more basic guidelines like
- formatting of commit messages
- creating tickets for each pull request
- make sure the changes in the commit adhere to the commit message and the corresponding ticket