Anti-censorship issueshttps://gitlab.torproject.org/groups/tpo/anti-censorship/-/issues2024-01-10T16:10:08Zhttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/190bridge-pool-assignment seems to often miss all webtunnel bridges2024-01-10T16:10:08Ztrinity-1686abridge-pool-assignment seems to often miss all webtunnel bridgesit seems most bridge-pool-assignment on collector contains no webtunnel bridges, despite such bridging existing and seemingly working.
Between `2023-12-11-00-20-28` and `2023-12-13-23-42-31`, 144 files have been generated, only 3 of whi...it seems most bridge-pool-assignment on collector contains no webtunnel bridges, despite such bridging existing and seemingly working.
Between `2023-12-11-00-20-28` and `2023-12-13-23-42-31`, 144 files have been generated, only 3 of which containing webtunnel bridges (`2023-12-11-22-50-28`, `2023-12-12-05-42-32` and `2023-12-11-22-20-28`, each containing 46 webtunnel bridges). It seems impossible that the reason is 46 bridges being alive for one period, and dead for every other, all in sync, so there is definitely some bug somewhere.
~~I haven't (yet) check further in the past to know if it was always like that, or when it started.~~
see belowmeskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40311Upgrade tor on snowflake bridges to 0.4.8.102024-01-07T16:00:05ZDavid Fifielddcf@torproject.orgUpgrade tor on snowflake bridges to 0.4.8.100.4.8.10 is a [security release](https://forum.torproject.org/t/security-release-0-4-8-10/10536)
for a vulnerability that I think doesn't affect us,
but more importantly it [fixes the user counting bug](https://gitlab.torproject.org/tpo/...0.4.8.10 is a [security release](https://forum.torproject.org/t/security-release-0-4-8-10/10536)
for a vulnerability that I think doesn't affect us,
but more importantly it [fixes the user counting bug](https://gitlab.torproject.org/tpo/core/tor/-/issues/40871#note_2975120)
that has existed since 0.4.8.4.
- [x] snowflake-01
- [x] snowflake-02
/cc @linusDavid Fifielddcf@torproject.orgDavid Fifielddcf@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40310Excessive logging in ordinary, non-verbose, log ("Proxy connection closed")2023-12-21T20:29:29ZLinus Nordberglinus@torproject.orgExcessive logging in ordinary, non-verbose, log ("Proxy connection closed")Since upgrading standalone proxies from v2.6.1 to v2.8.0, the (ordinary, non-verbose) log contains quite a few `Proxy connection closed` lines that were not there before.
Seems like the return value of `EventOnProxyConnectionOver.String...Since upgrading standalone proxies from v2.6.1 to v2.8.0, the (ordinary, non-verbose) log contains quite a few `Proxy connection closed` lines that were not there before.
Seems like the return value of `EventOnProxyConnectionOver.String()` (snowflake/common/event/interface.go:76 in v2.8.0) ends up in the log. Might be related to commit 648609dbea31d5ba604d00a7f765a1a47d673896 but I haven't looked closely.
Given that the `OnClose()` callback defined by the `OnDataChannel()` callback in `makePeerConnectionFromOffer()` (snowflake/proxy/lib/snowflake.go:401 in v2.8.0) does log `Data Channel %s-%d close\n` (when verbose logging is enabled), silencing the excessive logging to the non-verbose log shouldn't be a problem.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40308AMP cache rendezvous don't work in China2023-11-30T04:00:07ZcypherpunksAMP cache rendezvous don't work in ChinaBridge line:
```
snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://snowflake-broker.torproject.net/ ampcache=https://cdn.ampproject.org/ front=www.google.com...Bridge line:
```
snowflake 192.0.2.3:80 2B280B23E1107BB62ABFC40DDCC8824814F80A72 fingerprint=2B280B23E1107BB62ABFC40DDCC8824814F80A72 url=https://snowflake-broker.torproject.net/ ampcache=https://cdn.ampproject.org/ front=www.google.com ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 utls-imitate=hellorandomizedalpn
snowflake 192.0.2.4:80 8838024498816A039FCBBAB14E6F40A0843051FA fingerprint=8838024498816A039FCBBAB14E6F40A0843051FA url=https://snowflake-broker.torproject.net/ ampcache=https://cdn.ampproject.org/ front=www.google.com ice=stun:stun.l.google.com:19302,stun:stun.antisip.com:3478,stun:stun.bluesip.net:3478,stun:stun.dus.net:3478,stun:stun.epygi.com:3478,stun:stun.sonetel.com:3478,stun:stun.uls.co.za:3478,stun:stun.voipgate.com:3478,stun:stun.voys.nl:3478 utls-imitate=hellorandomizedalpn
```
log:
```
yyyy-mm-dd 22:35:45.077 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
yyyy-mm-dd 22:35:46.726 [NOTICE] Opening Socks listener on 127.0.0.1:9150
yyyy-mm-dd 22:35:46.726 [NOTICE] Opened Socks listener connection (ready) on 127.0.0.1:9150
yyyy-mm-dd 22:35:47.380 [NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
yyyy-mm-dd 22:35:47.381 [NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
yyyy-mm-dd 22:35:47.563 [NOTICE] Bootstrapped 10% (conn_done): Connected to a relay
yyyy-mm-dd 22:35:48.113 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:35:48.113 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:37:48.215 [NOTICE] Delaying directory fetches: No running bridges
yyyy-mm-dd 22:37:59.108 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:37:59.108 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:37:59.384 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:37:59.420 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:40:10.192 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:40:10.192 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:40:10.468 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:40:10.468 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:40:47.588 [NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
yyyy-mm-dd 22:40:47.593 [NOTICE] Our circuit 0 (id: 15) died due to an invalid selected path, purpose Unlinked conflux circuit. This may be a torrc configuration issue, or a bug.
yyyy-mm-dd 22:40:47.978 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:40:47.983 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:40:48.332 [NOTICE] Delaying directory fetches: No running bridges
yyyy-mm-dd 22:42:21.244 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:42:21.244 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:42:58.108 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:42:58.108 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:42:58.665 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:42:58.672 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:45:09.180 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:45:09.182 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:45:09.537 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:45:09.543 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:45:47.650 [NOTICE] Failed to find node for hop #1 of our path. Discarding this circuit.
yyyy-mm-dd 22:45:47.931 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:45:48.571 [NOTICE] Delaying directory fetches: No running bridges
yyyy-mm-dd 22:46:47.198 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:47:20.253 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:47:20.253 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:47:59.164 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:47:59.440 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:48:58.560 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:48:59.028 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:50:10.236 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:50:10.527 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:51:09.628 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": broker failure dial tcp [scrubbed]: connect: connection timed out
yyyy-mm-dd 22:51:09.932 [NOTICE] Managed proxy "./TorBrowser/Tor/PluggableTransports/snowflake-client": offer created
yyyy-mm-dd 22:51:46.864 [WARN] Problem bootstrapping. Stuck at 10% (conn_done): Connected to a relay. (DONE; DONE; count 6; recommendation warn; host 8838024498816A039FCBBAB14E6F40A0843051FA at 192.0.2.4:80)
yyyy-mm-dd 22:51:46.864 [WARN] 6 connections have failed:
yyyy-mm-dd 22:51:46.865 [WARN] 6 connections died in state handshaking (TLS) with SSL state SSLv3/TLS write client hello in HANDSHAKE
yyyy-mm-dd 22:51:46.873 [NOTICE] Closing no-longer-configured Socks listener on 127.0.0.1:9150
yyyy-mm-dd 22:51:46.873 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections.
yyyy-mm-dd 22:51:46.990 [WARN] Managed proxy "N/A" process terminated with status code 0
```https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40307WebRTC: ICE failed, add a TURN server and see about:webrtc for more details2023-11-26T16:42:30ZcypherpunksWebRTC: ICE failed, add a TURN server and see about:webrtc for more detailsI am not able to make skowflake working on my computer. (location - Czech Republic, Europe)
For a long time there is no connection going through it, but it is connected to the broker.
Here is the mozila firefox console log. (using https...I am not able to make skowflake working on my computer. (location - Czech Republic, Europe)
For a long time there is no connection going through it, but it is connected to the broker.
Here is the mozila firefox console log. (using https://snowflake.torproject.org/embed):
```Snowflake: == snowflake proxy == embed.js:1416:13
Snowflake: Disabling Snowflake. embed.js:1416:13
Snowflake: Currently not active. embed.js:1416:13
WebRTC: ICE failed, add a TURN server and see about:webrtc for more details
Snowflake: Starting snowflake embed.js:1416:13
Snowflake: Snowflake IDs: pmmql19l9jo embed.js:1416:13
Snowflake: Polling broker.. embed.js:1416:13
NAT type: unknown embed.js:649:13
Setting NAT type: restricted embed.js:1293:15
Snowflake: Snowflake IDs: 7fucxv3xnut embed.js:1416:13
Snowflake: Polling broker.. embed.js:1416:13
NAT type: restricted embed.js:649:13
Snowflake: Snowflake IDs: 75y6n5ptni2 embed.js:1416:13
Snowflake: Polling broker.. embed.js:1416:13
NAT type: restricted```https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/184Make the HTTP distributor's website localizable2024-03-20T13:51:15Zmeskiomeskio@torproject.orgMake the HTTP distributor's website localizablerdsys already has [translation support](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/tree/main/pkg/locales?ref_type=heads). Should we pass the strings to the templates from rdsys? Or should we look into another option more *...rdsys already has [translation support](https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/tree/main/pkg/locales?ref_type=heads). Should we pass the strings to the templates from rdsys? Or should we look into another option more *web-friendly*?shelikhooshelikhoo2024-03-08https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/183Import bridges.torproject.org web design2024-03-19T08:50:35Zmeskiomeskio@torproject.orgImport bridges.torproject.org web designBring the bridges.torproject.org web design into rdsys.Bring the bridges.torproject.org web design into rdsys.shelikhooshelikhoo2024-03-08https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/181Make circumvention settingsa anti-listing techniques reusable by HTTP2023-12-20T17:42:19Zmeskiomeskio@torproject.orgMake circumvention settingsa anti-listing techniques reusable by HTTPWe want to deprecate captchas (#173) and reuse the same techniques used by circumvention settings in the HTTP distributor.We want to deprecate captchas (#173) and reuse the same techniques used by circumvention settings in the HTTP distributor.meskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/40Lox distributor panics on user request2023-12-18T19:39:17ZCecylia BocovichLox distributor panics on user requestI just took a look at the logs after trying to use the lox distributor and getting a 502 error. This is what I saw:
```plaintext
Nov 20 17:37:07 rdsys-frontend-01 lox-distributor[1794548]: thread 'tokio-runtime-worker' panicked at crate...I just took a look at the logs after trying to use the lox distributor and getting a 502 error. This is what I saw:
```plaintext
Nov 20 17:37:07 rdsys-frontend-01 lox-distributor[1794548]: thread 'tokio-runtime-worker' panicked at crates/lox-distributor/src/main.rs:344:44:
Nov 20 17:37:07 rdsys-frontend-01 lox-distributor[1794548]: called `Result::unwrap()` on an `Err` value: SendError { .. }
Nov 20 17:38:31 rdsys-frontend-01 lox-distributor[1794548]: thread 'tokio-runtime-worker' panicked at crates/lox-distributor/src/main.rs:344:44:
Nov 20 17:38:31 rdsys-frontend-01 lox-distributor[1794548]: called `Result::unwrap()` on an `Err` value: SendError { .. }
```Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/gettor-project/OnionSproutsBot/-/issues/57TB for MacOS obtained from the gettor_bot (Telegram) did not work2023-11-16T11:34:58ZninaTB for MacOS obtained from the gettor_bot (Telegram) did not workOS: MacOS
Problem:
Two users reported they downloaded TB for MacOS from @gettor_bot on Telegram and got an error message (The application cannot be open) while trying to install it.
When they downloaded TB from our website (to be preci...OS: MacOS
Problem:
Two users reported they downloaded TB for MacOS from @gettor_bot on Telegram and got an error message (The application cannot be open) while trying to install it.
When they downloaded TB from our website (to be precise - from the mirror) - the installation competed without errors.https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40306Log scrubber fails to scrub messages with multiple space-separated IP addresses2024-01-08T15:04:55ZCecylia BocovichLog scrubber fails to scrub messages with multiple space-separated IP addressesI noticed this while looking at the conjure server logs. The following diff introduces a failing unit test for this case:
```diff
diff --git a/common/safelog/log_test.go b/common/safelog/log_test.go
index b6a719e..267538c 100644
--- a/co...I noticed this while looking at the conjure server logs. The following diff introduces a failing unit test for this case:
```diff
diff --git a/common/safelog/log_test.go b/common/safelog/log_test.go
index b6a719e..267538c 100644
--- a/common/safelog/log_test.go
+++ b/common/safelog/log_test.go
@@ -107,6 +107,11 @@ func TestLogScrubberMessages(t *testing.T) {
"error dialing relay: wss://snowflake.torproject.net/?client_ip=1%3A2%3A3%3A%3Ad%3Ae%3Af = dial tcp xxx",
"error dialing relay: wss://snowflake.torproject.net/?client_ip=[scrubbed] = dial tcp xxx\n",
},
+ {
+ // multiple space-separated IP addresses
+ "Allowed stations: [10.0.1.1 10.0.1.2 10.0.1.3 10.0.1.4]\n",
+ "Allowed stations: [[scrubbed] [scrubbed] [scrubbed] [scrubbed]]\n",
+ },
} {
var buff bytes.Buffer
log.SetFlags(0) //remove all extra log output for test comparisons
```https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/39Add 10.0.1.7 to allowed ips at conjure server2023-11-08T16:12:14ZCecylia BocovichAdd 10.0.1.7 to allowed ips at conjure serverThere has been a new wireguard peer at `10.0.1.7`. Looking at the timestamp on `/etc/wireguard/wg0.conf`, it looks like it was added on September 25th.There has been a new wireguard peer at `10.0.1.7`. Looking at the timestamp on `/etc/wireguard/wg0.conf`, it looks like it was added on September 25th.Cecylia BocovichCecylia Bocovichhttps://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/179update "Get Bridges" instruction on the email we send out with GetTor email r...2023-11-07T16:52:51Zebanamebanam@torproject.orgupdate "Get Bridges" instruction on the email we send out with GetTor email requestsCurrent version:
> Step 3: Get Bridges (Optional)
If you believe that Tor is blocked where you are, you can use bridges to connect
to Tor. Bridges are hidden Tor relays that can circumvent censorship.
Tor Browser...Current version:
> Step 3: Get Bridges (Optional)
If you believe that Tor is blocked where you are, you can use bridges to connect
to Tor. Bridges are hidden Tor relays that can circumvent censorship.
Tor Browser includes a list of built-in bridges, which you should try first.
You can activate built-in bridges inside of Tor Browser's settings, under the
"Tor" menu. If built-in bridges don't work, try requesting different bridges,
which you can also do in the "Tor" menu inside Tor Browser's settings.
Update:
You can activate built-in bridges inside of Tor Browser's settings, under the
"Connection" menu. If built-in bridges don't work, try requesting different bridges,
which you can also do in the "Connection" menu inside Tor Browser's settings.
(thanks to @nina for noticing this!)https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/87unify volunteer instructions from support entry onto snowflake website2024-02-27T13:16:49ZRoger Dingledineunify volunteer instructions from support entry onto snowflake websiteWe have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension ...We have this support entry: <br>
https://support.torproject.org/censorship/how-to-help-running-snowflake/
which tells people to install the Firefox or Chrome extension, or load the embed in a page. It doesn't mention the Edge extension or the standalone proxy.
Rather than trying to keep both sets of instructions in sync, I think we should put the instructions on the snowflake.torproject.org page, and point to them from a much slimmer support entry.
To achieve this goal, there are currently two things that the support entry says that the snowflake.torproject.org website does not:
* You need to enable WebRTC in your browser, to usefully run the extension or to usefully load the embed. (If we could reliably have the extension or the embed page report that your WebRTC is missing and you need to fix that, then we could get away with not saying it on the webpage. So, feel free to do that instead if it is easier, but I am suspecting it is not easier. :)
* "Due to censorship of VPN servers in some countries, we kindly ask you to not run a snowflake proxy while connected to a VPN" as advised by @cohosh at https://forum.torproject.org/t/running-a-snowflake-proxy-behind-a-vpn-consequences-for-tor-users/2047/4 and then recorded by gus at https://gitlab.torproject.org/tpo/web/support/-/issues/296. Feel free also to change your mind about the "not on a VPN please" advice.
Once we have these two items either make their way onto the snowflake.torproject.org proxy instructions or have you tell us you don't intend to, then we should be all ready to remove the (redundant, already not as correct) text from the support entry.
Thanks!https://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/38Update Lox Distributor Config file to request Lox type2023-11-09T03:49:09ZonyinyangUpdate Lox Distributor Config file to request Lox typeThis should work in tandem with an update to `rdsys` that partitions bridges in to a `lox` type. This will only require an update to the test config file in the lox-distributor repo but this issue is mostly a reminder to update once a `l...This should work in tandem with an update to `rdsys` that partitions bridges in to a `lox` type. This will only require an update to the test config file in the lox-distributor repo but this issue is mostly a reminder to update once a `lox` type exists.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/37Publish Lox crates on crates.io2023-11-23T18:05:31ZonyinyangPublish Lox crates on crates.ioPrior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to ...Prior to Lox being deployed, we should publish each of the Lox crates on [`crates.io`](https://crates.io/). The crate name and the `crates.io` name should match to avoid confusion/inconvenience.
There are instructions for publishing to `crates.io` [here](https://doc.rust-lang.org/cargo/reference/publishing.html)
Once the crates are created, we should update our pipeline to automatically push updates to the documentation as appropriate.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40305Upgrade tor on snowflake bridges to 0.4.8.8 for TROVE 2023 0042023-11-07T00:11:57ZDavid Fifielddcf@torproject.orgUpgrade tor on snowflake bridges to 0.4.8.8 for TROVE 2023 004https://lists.torproject.org/pipermail/tor-relays/2023-November/021373.html
> Today (2023-11-03) the Network Team has released [new Tor versions 0.4.7.16 and 0.4.8.8](https://forum.torproject.org/t/security-release-0-4-7-16-and-0-4-8-8/...https://lists.torproject.org/pipermail/tor-relays/2023-November/021373.html
> Today (2023-11-03) the Network Team has released [new Tor versions 0.4.7.16 and 0.4.8.8](https://forum.torproject.org/t/security-release-0-4-7-16-and-0-4-8-8/10064). These updates contains a fix to a remote crash bug (TROVE 2023 004). It is highly recommended that all relay operators upgrade to the new versions as soon as possible to maintain the network stability and security.
>
> For those running their Tor relay using the Tor Debian repository, expect the new deb package to be available soon.
>
> The patches prevents the issue from causing a crash in Tor. However, it will make Tor more noisy when the bug is triggered, including logging information about the remote peer that is the source or destination of the circuit in the path. Such information is important for our developers to diagnose the specific invariant within Tor's TLS logic that does not hold.
- [x] snowflake-01
- [x] snowflake-02
/cc @linusDavid Fifielddcf@torproject.orgDavid Fifielddcf@torproject.org2023-11-06https://gitlab.torproject.org/tpo/anti-censorship/gettor-project/OnionSproutsBot/-/issues/55@gettor_bot on Telegram does not work2023-11-06T12:01:00Znina@gettor_bot on Telegram does not workIt does not react to the commands.
Reported by two users and confirmed by meIt does not react to the commands.
Reported by two users and confirmed by memeskiomeskio@torproject.orgmeskiomeskio@torproject.orghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/36Some bridgelines are not found in db after being added2024-01-17T17:15:58ZonyinyangSome bridgelines are not found in db after being addedThere seems to be a bug in the `lox-distributor` that occurs on the first sync with rdsys after a new Lox context is established. Several test bridge fingerprints are listed as `not found in Lox's Bridgetable. Save it as a new resource f...There seems to be a bug in the `lox-distributor` that occurs on the first sync with rdsys after a new Lox context is established. Several test bridge fingerprints are listed as `not found in Lox's Bridgetable. Save it as a new resource for now!' but this only happens for new databases and only on the first sync. It may not be a problem but should be looked into before Lox is ready for prod.onyinyangonyinyanghttps://gitlab.torproject.org/tpo/anti-censorship/lox/-/issues/35Create a telegram distributor for open invitations with rate limiting through...2024-01-08T15:49:44ZonyinyangCreate a telegram distributor for open invitations with rate limiting through the age of accountsFrom the [Lox Roadmap](https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/wikis/Lox-Roadmap) we want a telegram bot that can be used to request Lox open invitations.From the [Lox Roadmap](https://gitlab.torproject.org/tpo/anti-censorship/lox-rs/-/wikis/Lox-Roadmap) we want a telegram bot that can be used to request Lox open invitations.onyinyangonyinyang