#21136: obfs4proxy doesn't listen on both 0.0.0.0 and [::]
-----------------------------------+-------------------------
Reporter: kaie | Owner: kaie
Type: defect | Status: closed
Priority: Medium | Milestone:
Component: Obfuscation/Obfsproxy | Version:
Severity: Normal | Resolution: wontfix
Keywords: | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
-----------------------------------+-------------------------
Comment (by dcf):
Replying to [comment:6 yawning]:
> * How `TOR_PT_SERVER_TRANSPORT_OPTIONS` should be handled is unclear.
The way goptlib is implemented now, it only supports a single set of
arguments per transport, which is likely incorrect.
What do you mean by this? I don't see how
`TOR_PT_SERVER_TRANSPORT_OPTIONS` could be split into more than one set of
arguments for each transport. Each key=value pair is tagged with the name
of the transport it belongs to, with no other distinguishing information.
The example from the spec is
{{{
TOR_PT_SERVER_TRANSPORT_OPTIONS=scramblesuit:key=banana;automata:rule=110;automata:depth=3
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/21136#comment:7>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online