Opened 7 years ago

Last modified 2 weeks ago

#5304 new defect

Obfsproxy should respect OutboundBindAddress in torrc

Reported by: korobkov Owned by:
Priority: Medium Milestone:
Component: Obfuscation/Obfsproxy Version:
Severity: Normal Keywords: needs-spec-change needs-tor-change
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Rather it just binds to * (any IP).

Tested with latest git obfsproxy and Tor 0.2.3.12-alpha.

Child Tickets

Change History (6)

comment:1 Changed 5 years ago by asn

Resolution: wontfix
Status: newclosed

We have the torrc ServerTransportListenAddr directive these days.
It should work for this use case.

comment:2 Changed 5 years ago by arma

Isn't the ListenAddr dictate how to bind your listening connection, and outboundbindaddress dictates how to bind your outgoing connection? They sure sound like different things.

comment:3 Changed 5 years ago by asn

Keywords: needs-spec-change needs-tor-change added
Resolution: wontfix
Status: closedreopened

Ah, indeed.
This sounds like a legitimate use case then.

We will probably need a pt-spec.txt change for this. TOR_PT_SERVER_BINDADDR specifies the listening bind address.

comment:4 Changed 15 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:5 Changed 3 weeks ago by teor

Owner: asn deleted
Status: reopenedassigned

asn does not need to own any obfuscation tickets any more. Default owners are trouble.

comment:6 Changed 2 weeks ago by cohosh

Status: assignednew

tickets are unassigned, reverting to 'new'

Note: See TracTickets for help on using tickets.