Opened 3 years ago

Last modified 3 years ago

#11574 new defect

flashproxy-client needs to support SOCKS arguments primarily

Reported by: infinity0 Owned by: dcf
Priority: Medium Milestone:
Component: Archived/Flashproxy Version:
Severity: Keywords:
Cc: RushingWookie Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by infinity0)

At the moment, flashproxy-client takes a bunch of command-line arguments, that determine how it registers and talks to the bridge.

These should really be done in the Bridge line (and passed in via SOCKS arguments), since the argument values may change per Bridge. These include:

--facilitator, --facilitator-pubkey
--register, --register-*
--transport.

I would argue that the CLI arguments be deprecated. I would favour complete removal, but AIUI it is required for compatibility with older versions of Tor.

This may require #10671.

Child Tickets

Change History (2)

comment:1 Changed 3 years ago by infinity0

Description: modified (diff)

comment:2 Changed 3 years ago by infinity0

Cc: RushingWookie added

add RushingWookie to cc

This will be relevant for the combiner - atm obfs3_flashproxy() in obfs-flash-client hardcodes "--transport=obfs3|websocket" but this means we can only use a single flashproxy process for one chain.

Ideally we would be able to tunnel both fteproxy|websocket and obfs3|websocket traffic through one single flashproxy process.

(scramblesuit|websocket will require #10196 due to bridge-specific secret)

Note: See TracTickets for help on using tickets.