#30350: Hello, in China, currently, Tor Browser 8.5a11 version can't connect to Tor network through Snowflake bridge. -----------------------------------+-------------------------- Reporter: amiableclarity2011 | Owner: cohosh Type: defect | Status: accepted Priority: Medium | Milestone: Component: Obfuscation/Snowflake | Version: Severity: Normal | Resolution: Keywords: | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: -----------------------------------+--------------------------
Comment (by dcf): Replying to [comment:10 cohosh]: > This makes sense to me, I think we do need to do something about item 2 as well though. I wasn't able to test the behaviour of tor browser at the VPS but just the Tor client was having trouble quickly deciding whether or not the proxy was being blocked. I suppose this won't be as big an issues when we have more diverse proxies though. No disagreement there. Snowflake can do better about detecting a lack of connectivity. Actually it's kind of a general thing that affects more than just Snowflake. See #24640 for meek for example. The PT interface was designed with a mindset of obfs4-like transport that make a single TCP connection to a single bridge and always have a well-defined connectedness state--it doesn't map perfectly onto transports that don't work like that. I think there are bugs on the tor side as well--see comment:3:ticket:26891 where deleting a state file made the connection start working, which looks like #11301 even though that is supposed to be fixed. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/30350#comment:11> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs