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

[Tor Bug Tracker & Wiki]

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

 * owner:  (none) => dcf
 * status:  new => assigned


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

[Tor Bug Tracker & Wiki]

#25723: Multiplex - one client splits traffic across multiple proxies
---+
 Reporter:  dcf|  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Low|  Milestone:
Component:  Obfuscation/Snowflake  |Version:
 Severity:  Normal |   Keywords:
Actual Points: |  Parent ID:
   Points: |   Reviewer:
  Sponsor: |
---+
 This is the dual of #25601.

 It would be a great feature if a client could be connected to multiple
 snowflake proxies at once, and split traffic across all of them. Like the
 [http://cacr.uwaterloo.ca/techreports/2013/cacr2013-16.pdf Conflux]
 proposal for Tor. It would be a hedge against getting assigned a single
 slow proxy.

 This would require interposing some kind of sequencing and reliability
 layer, with possible retransmissions.

 A potential benefit for privacy is that an individual snowflake proxy only
 sees a subset of a client's traffic flow.

 However, instantly making ''N'' WebRTC connections is a tell for traffic
 classification.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs