Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#12605 closed defect (fixed)

obfs4 bridges should autogenerate keys when invoked with no arguments.

Reported by: yawning Owned by: yawning
Priority: Medium Milestone:
Component: Circumvention/Pluggable transport Version:
Severity: Keywords: obfs4
Cc: asn Actual Points:
Parent ID: #12130 Points:
Reviewer: Sponsor:


After talking with certain people at the dev meeting, I am convinced that having obfs4proxy autogenerate keys when invoked with no arguments when running as a bridge will be a good idea. I anticipate that this will be less problematic than the similar codepath in scramblesuit as the code has no need to support unmanaged mode.

The current plan is to store the keypair in the pt state directory in what will probably be JSON format so that it is easy-ish for bridge operators to obtain the bridge line for clients at a later date

Child Tickets

Change History (2)

comment:1 Changed 6 years ago by yawning

Resolution: fixed
Status: newclosed

Fixed in 339c63f0c8cd4374f6fa26484498eb6fa91b7bca, exactly as stated in the ticket. A JSON file will be placed in the pt_state directory containing an autogenerated set of arguments (and the public-key for the client), and an attempt will be made to load said state file if no arguments are passed.

comment:2 Changed 6 years ago by libinhua2012

Why obfs4 is no need to support unmanaged mode? I was hopping obfs4 will obfuscate my shadowsocks traffic.

Note: See TracTickets for help on using tickets.