Networking on Tails #810

New Issue

domelike · 2024-02-02T23:13:04Z

domelike commented

2024-02-02 23:13:04 +00:00

On the most recent version of Tails (5.22), Tor doesn't connect. I tested from two different laptops. Here is the relevant output:

2024/02/02 21:48:26 cwtch-autobindings/lib.go [INFO] CWTCH_TAILS environment variable set... overriding tor config...
2024/02/02 21:48:26 tor/torProvider.go [INFO] tor version: 0.4.8.9
2024/02/02 21:49:11 cwtch-autobindings/lib.go [ERR ] Error connecting to Tor replacing with ErrorACN: Error on start: dial tcp 127.0.0.1:9051: connect: connection refused (also got error trying to close: Process wait failed: exit status 1)
2024/02/02 21:49:11 cwtch-autobindings/lib.go [INFO] Restarted

On the most recent version of Tails (5.22), Tor doesn't connect. I tested from two different laptops. Here is the relevant output: ``` 2024/02/02 21:48:26 cwtch-autobindings/lib.go [INFO] CWTCH_TAILS environment variable set... overriding tor config... 2024/02/02 21:48:26 tor/torProvider.go [INFO] tor version: 0.4.8.9 2024/02/02 21:49:11 cwtch-autobindings/lib.go [ERR ] Error connecting to Tor replacing with ErrorACN: Error on start: dial tcp 127.0.0.1:9051: connect: connection refused (also got error trying to close: Process wait failed: exit status 1) 2024/02/02 21:49:11 cwtch-autobindings/lib.go [INFO] Restarted ```

sarah added the

bug

tails

labels 2024-02-02 23:29:46 +00:00

sarah self-assigned this 2024-02-04 04:29:42 +00:00

sarah commented

2024-02-12 17:44:08 +00:00

Replicated this issue. Investigating the cause...

sarah commented

2024-02-12 18:33:17 +00:00

Looks like Tails changed the Tor control port from 9051 to 951. 50afb92b71

This can be temporarily mitigated by editing the cwtch launcher script (usually in ~/.local/bin/cwtch to remove CWTCH_TAILS=true and then by enabled Advanced Tor Configuration in Cwtch and manually setting the control port to 951 and socks port to 9050 (and then restarting Cwtch)

This is enough to get Cwtch functional in tails 5.22.

We will patch the CWTCH_TAILS variable to do this automatically.

Looks like Tails changed the Tor control port from 9051 to 951. https://gitlab.tails.boum.org/tails/tails/-/commit/50afb92b71fadc03984853d10bda61a2ba2fd9f4 This can be temporarily mitigated by editing the cwtch launcher script (usually in `~/.local/bin/cwtch` to remove `CWTCH_TAILS=true` and then by enabled `Advanced Tor Configuration` in Cwtch and manually setting the control port to `951` and socks port to `9050` (and then restarting Cwtch) This is enough to get Cwtch functional in tails 5.22. We will patch the CWTCH_TAILS variable to do this automatically.

sarah commented

2024-02-12 19:14:16 +00:00

cwtch.im/autobindings#57

https://git.openprivacy.ca/cwtch.im/autobindings/pulls/57

sarah referenced this issue from a commit

2024-02-13 19:07:41 +00:00

Upgrade libCwtch to fix #810

sarah referenced this issue from a commit

2024-02-13 19:08:18 +00:00

Upgrade libCwtch to fix #810

sarah referenced a pull request that will close this issue

2024-02-13 19:08:26 +00:00