[tor-bugs] #25723 [Circumvention/Snowflake]: Multiplex - one client splits traffic across multiple proxies

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Feb 4 12:19:05 UTC 2020


#25723: Multiplex - one client splits traffic across multiple proxies
-------------------------------------+--------------------------
 Reporter:  dcf                      |          Owner:  dcf
     Type:  defect                   |         Status:  assigned
 Priority:  Low                      |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+--------------------------

Comment (by uiouio27):

 I am bit confused, after reading the technical documentation of Snowflake
 (https://keroserene.net/snowflake/technical/#35--recovery-and-
 multiplexing). In the "Recovery and Multiplexing" section it says: "...In
 any case, snowflake seeks to maintain high reliability and connectivity,
 and a high quality browsing experience for the user in the Tor Browser
 use-case, by having snowflake clients and proxies multiplex each other.
 When an individual WebRTC DataChannel fails, the snowflake client renews
 with a new WebRTC peer...". Does that mean that the required feature is
 covered? As far as I understand, that would switch the connection when a
 proxy leaves but not when it is very slow. Would it be still convenient to
 utilize several proxies but coordinately and congestion-based sending
 traffic to them?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/25723#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online


More information about the tor-bugs mailing list