All pluggable transports stopped working after 11-06-2020

[phabricator-migrator]

Information

ID: 997
PHID: PHID-TASK-vf2s6pt5legplxcqh4qs
Author: leh6r0
Status at Migration Time: invalid
Priority at Migration Time: Normal

Description

Did pluggable transports stop working for you?

(I’m using Whonix with Qubes 4) After 11/06, it seems that all pluggable transports stopped working for me. I used to use snowflake and then it stopped working, and when I change the torrc file for Whonix to obfs4 it also doesn’t work. Can anyone else try to reproduce this? BTW I opened a ticket for that here: T997 All pluggable transports stopped working after 11-06-2020

(Setup: Qubes 4 + Whonix)

I followed the Whonix wiki’s snowflake in setting up Snowflake:

Configure (Private) (Obfuscated) Tor Bridges

It was always working before 11-06 and I never had a problem. However after updating snowflake-client and updating Whonix something happened that made stop working. I don’t think the problem comes from snowflake-client itself since it works fine with a fresh debian-9 Qubes VM.

Looking at the logs this is where it gets stuck:

[NOTICE] New control connection opened.
[NOTICE] Bootstrapped 2% (conn_done_pt): Connected to pluggable transport
[NOTICE] Bootstrapped 1% (conn_pt): Connecting to pluggable transport
[NOTICE] Tor 0.4.2.7 opening log file.

Edit: It seems this is not just snowflake specific, I tried to use some obfs4 bridges and it didn’t work!

Comments

---

leh6r0

2020-06-21 08:34:06 UTC

Don’t know if this is indicative of anything but after I add -log snowflake-client.log -log-to-state-dir at the end of the ClientTransportPlugin snowflake line in /usr/local/etc/torrc.d/50_user.conf I obtain the following error:

 [WARN] Pluggable Transport process terminated with status code 512 [1 duplicate hidden]
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: URL of signaling broker
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -url string
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: capacity for number of multiplexed
   WebRTC peers (default 1)
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -max int
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: resolve the log file relative to tor's
   pt state dir
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -logToStateDir
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: name of log file
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -log string
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: comma-separated list of ICE servers
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -ice string
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: front domain
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: -front string
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: Usage of /usr/bin/snowflake-client:
 [WARN] Managed proxy at '/usr/bin/snowflake-client' reported: flag provided but not defined:
   -log-to-state-dir

So it seems there might be something that terminates the snowflake-client process.

---

leh6r0

2020-06-24 11:51:24 UTC

More useful information from my tests: When I setup obfs4 using the Anon-Connection-Wizard the previous obfs4 that I used worked fine. Unfortunately I can’t setup snowflake from it.

---

Patrick

2020-06-25 09:29:46 UTC

Thanks for the report.

This issue tracker is legacy as per:
Bug Reports, Software Development and Feature Requests

Therefore closing here and continuing in forums.

Did pluggable transports stop working for you?