Opened 18 months ago

Last modified 2 months ago

#25601 new defect

Multiplex - one snowflake proxy should be able to support multiple clients

Reported by: arlolra Owned by:
Priority: Medium Milestone:
Component: Circumvention/Snowflake Version:
Severity: Normal Keywords: snowflake, tor-pt, anti-censorship-roadmap-september
Cc: dcf, arlolra, cohosh Actual Points:
Parent ID: Points: 2
Reviewer: Sponsor: Sponsor28-can

Description

Migrated from https://github.com/keroserene/snowflake/issues/11

This seems to exist for the proxy-go but the JavaScript side has things like,

MAX_NUM_CLIENTS = 1
CONNECTIONS_PER_CLIENT = 1

so I'm guessing it wasn't finished.

Child Tickets

Change History (6)

comment:1 Changed 10 months ago by arma

Dcf points out that this ticket isn't as urgent as it might seem, (a) because the headless proxy-go can already handle multiple clients at once, and (b) because the vision is that we'll have way way more snowflakes than clients, so most snowflakes will be idle most of the time, so the chances of a collision (more than one client sent to the same snowflake) are low.

I buy this logic in the short term, but it still seems to me that the broker design will get cleaner if the browser snowflakes can handle whichever clients try to use them, even if two show up together.

comment:2 Changed 9 months ago by gaba

Keywords: snowflake tor-pt added
Sponsor: Sponsor19

comment:3 Changed 4 months ago by gaba

Keywords: ex-sponsor-19 added

Adding the keyword to mark everything that didn't fit into the time for sponsor 19.

comment:4 Changed 4 months ago by phw

Sponsor: Sponsor19Sponsor28-can

Moving from Sponsor 19 to Sponsor 28.

comment:5 Changed 2 months ago by gaba

Cc: cohosh added
Keywords: anti-censorship-roadmap-september added; ex-sponsor-19 removed

comment:6 Changed 2 months ago by gaba

Points: 2
Note: See TracTickets for help on using tickets.